feat(docs): docs for both UA and LDAP lockout

docs/documentation/platform/identities/ldap-auth/general.mdx

@@ -34,24 +34,33 @@ To create and manage LDAP auth templates, see our [Machine Identity Auth Templat
     To configure LDAP auth for your identity, press the **Add Auth Method** button on the identity's page.
 
     ![Add auth method](/images/platform/identities/ldap/identities-org-add-auth-method.png)
-    
+
     Now select **LDAP Auth** from the list of available auth methods for the identity.
 
     ![Select LDAP auth](/images/platform/identities/ldap/identities-org-add-auth-method-modal.png)
-    
-    
+
+
     After selecting **LDAP Auth**, you'll see the form you need to fill out to configure LDAP auth for your identity. The following fields are available:
 
+    **Configuration Tab**
     - `URL`: The LDAP server to connect to such as `ldap://ldap.your-org.com`, `ldaps://ldap.myorg.com:636` _(for connection over SSL/TLS)_, etc.
     - `Bind DN`: The DN to bind to the LDAP server with.
     - `Bind Pass`: The password to bind to the LDAP server with.
     - `Search Base / DN`: Base DN under which to perform user search such as `ou=Users,dc=acme,dc=com`.
     - `User Search Filter`: Template used to construct the LDAP user search filter such as `(uid={{username}})`; use literal `{{username}}` to have the given username used in the search. The default is `(uid={{username}})` which is compatible with several common directory schemas.
     - `Required Attributes`: A key/value pair of attributes that must be present in the LDAP user entry for them to be authenticated. As an example, if you set key `uid` to value `user1,user2,user3`, then only users with `uid` of `user1`, `user2`, or `user3` will be able to login with this identity. Each value is a comma separated list of attributes.
-    - `CA Certificate`: The CA certificate to use when verifying the LDAP server certificate. This field is optional but recommended.
     - `Access Token TTL` _(default is 2592000 equivalent to 30 days)_: The lifetime for an access token in seconds. This value will be referenced at renewal time.
     - `Access Token Max TTL` _(default is 2592000 equivalent to 30 days)_: The maximum lifetime for an access token in seconds. This value will be referenced at renewal time.
     - `Access Token Max Number of Uses` _(default is 0)_: The maximum number of times that an access token can be used; a value of 0 implies infinite number of uses.
+
+    **Lockout Tab**
+    - `Lockout` _(enabled by default)_: The lockout feature will temporarily block login attempts for a specific identity auth method after X consecutive login failures.
+    - `Lockout Threshold` _(default is 3)_: The amount of times login must fail before locking the identity auth method.
+    - `Lockout Duration` _(default is 5 minutes)_: How long an identity auth method lockout lasts.
+    - `Lockout Counter Reset` _(default is 30 seconds)_: How long to wait from the most recent failed login until resetting the lockout counter.
+
+    **Advanced Tab**
+    - `CA Certificate`: The CA certificate to use when verifying the LDAP server certificate. This field is optional but recommended.
     - `Access Token Trusted IPs`: The IPs or CIDR ranges that access tokens can be used from. By default, each token is given the 0.0.0.0/0, allowing usage from any network address.
 
     Once you've filled out the form, press **Add** to save your changes.
@@ -91,3 +100,13 @@ To create and manage LDAP auth templates, see our [Machine Identity Auth Templat
     </Step>
   </Step>
 </Steps>
+
+**FAQ**
+
+<AccordionGroup>
+    <Accordion title="How do I reset a lockout?">
+        You can reset (remove) all lockouts for an identity auth method by clicking into the auth method and pressing **Reset All Lockouts**.
+
+        ![ldap reset lockouts](/images/platform/identities/ldap-reset-lockouts.png)
+    </Accordion>
+</AccordionGroup>

docs/documentation/platform/identities/universal-auth.mdx

@@ -4,7 +4,7 @@ description: "Learn how to authenticate to Infisical from any platform or enviro
 ---
 
 **Universal Auth** is a platform-agnostic authentication method that can be configured for a [machine identity](/documentation/platform/identities/machine-identities) to authenticate from any platform/environment using a Client ID and Client Secret.
-This authentication method supports setting token periods, which can help [overcome secret zero](#solving-secret-zero-with-periodic-tokens). 
+This authentication method supports setting token periods, which can help [overcome secret zero](#solving-secret-zero-with-periodic-tokens).
 
 ## Diagram
 
@@ -67,15 +67,25 @@ using the Universal Auth authentication method.
 
     ![identities organization create universal auth method 1](/images/platform/identities/identities-org-create-universal-auth-method-1.png)
     ![identities organization create universal auth method 2](/images/platform/identities/identities-org-create-universal-auth-method-2.png)
+    ![identities organization create universal auth method 3](/images/platform/identities/identities-org-create-universal-auth-method-3.png)
 
     Here's some more guidance on each field:
 
-    - Access Token TTL (default is `2592000` equivalent to 30 days): The lifetime for an acccess token in seconds. This value will be referenced at renewal time.
-    - Access Token Max TTL (default is `2592000`  equivalent to 30 days): The maximum lifetime for an acccess token in seconds. This value will be referenced at renewal time.
+    **Configuration Tab**
+    - Access Token TTL (default is `2592000` equivalent to 30 days): The lifetime for an access token in seconds. This value will be referenced at renewal time.
+    - Access Token Max TTL (default is `2592000`  equivalent to 30 days): The maximum lifetime for an access token in seconds. This value will be referenced at renewal time.
     - Access Token Max Number of Uses (default is `0`): The maximum number of times that an access token can be used; a value of `0` implies infinite number of uses.
+    - Access Token Period (optional, default is `0`): If set, the access token becomes a renewable, non-expiring token for the specified period (in seconds). TTL and Max TTL are ignored when this is set. This is ideal for "secret zero" scenarios, where a workload needs to bootstrap itself securely without hard-coded static secrets.
+
+    **Lockout Tab**
+    - Lockout (enabled by default): The lockout feature will temporarily block login attempts for a specific identity auth method after X consecutive login failures.
+    - Lockout Threshold (default is `3`): The amount of times login must fail before locking the identity auth method.
+    - Lockout Duration (default is `5 minutes`): How long an identity auth method lockout lasts.
+    - Lockout Counter Reset (default is `30 seconds`): How long to wait from the most recent failed login until resetting the lockout counter.
+
+    **Advanced Tab**
     - Client Secret Trusted IPs: The IPs or CIDR ranges that the **Client Secret** can be used from together with the **Client ID** to get back an access token. By default, **Client Secrets** are given the `0.0.0.0/0`, allowing usage from any network address.
     - Access Token Trusted IPs: The IPs or CIDR ranges that access tokens can be used from. By default, each token is given the `0.0.0.0/0`, allowing usage from any network address.
-    - Access Token Period (optional, default is `0`): If set, the access token becomes a renewable, non-expiring token for the specified period (in seconds). TTL and Max TTL are ignored when this is set. This is ideal for "secret zero" scenarios, where a workload needs to bootstrap itself securely without hard-coded static secrets.
 
     <Warning>
     Restricting **Client Secret** and access token usage to specific trusted IPs is a paid feature.
@@ -202,6 +212,10 @@ This approach allows your workload to securely bootstrap and maintain access to
 
     A token can be renewed any number of times where each call to renew it can extend the token's lifetime by increments of the access token's TTL.
     Regardless of how frequently an access token is renewed, its lifespan remains bound to the maximum TTL determined at its creation.
+  </Accordion>
+  <Accordion title="How do I reset a lockout?">
+      You can reset (remove) all lockouts for an identity auth method by clicking into the auth method and pressing **Reset All Lockouts**.
 
+      ![ua reset lockouts](/images/platform/identities/ua-reset-lockouts.png)
   </Accordion>
 </AccordionGroup>