Merge branch '4.6.0' of github.com:wso2/docs-apim into 4.6.0

Author: dushaniw

en/docs/administer/managing-users-and-roles/managing-user-stores/writing-a-custom-user-store-manager.md

@@ -517,6 +517,22 @@ in your WSO2 product.
         different primary user store configured. For more information
         configuring user stores in WSO2 products, see [Configuring User
         Stores]({{base_path}}/administer/product-administration/managing-users-and-roles/managing-user-stores/configuring-secondary-user-stores/).
+
+    **Adding custom user store as a secondary user store**
+
+    If you need to add the custom user store as a **secondary** user store, you must use one of the following configurations in the `<API-M_HOME>/repository/conf/deployment.toml` file instead of the configuration shown above:
+
+    **Option 1:** Add to the allowed user stores list
+    ``` toml
+    [user_store_mgt]
+    allowed_user_stores=["org.wso2.carbon.user.core.jdbc.UniqueIDJDBCUserStoreManager", "org.wso2.carbon.user.core.ldap.UniqueIDActiveDirectoryUserStoreManager","org.wso2.carbon.user.core.ldap.UniqueIDReadOnlyLDAPUserStoreManager","org.wso2.carbon.user.core.ldap.UniqueIDReadWriteLDAPUserStoreManager","org.wso2.custom.user.store.CustomUserStoreManager"]
+    ```
+
+    **Option 2:** Add to the custom user stores list
+    ``` toml
+    [user_store_mgt]
+    custom_user_stores=["org.wso2.custom.user.store.CustomUserStoreManager"]
+    ```
 
 
     You do not need to change anything else since you extend the
@@ -528,6 +544,10 @@ Once you have done this, start the product and see the log messages that
 you have placed inside overridden methods when you create a new user or
 login. This ensures that all your configurations work as intended.
 
+## Sample implementations
+
+For additional reference and sample implementations, see the [sample custom user store manager](https://github.com/wso2/product-is/tree/v5.10.0/modules/samples/user-mgt/sample-custom-user-store-manager) available in the WSO2 Identity Server repository. This sample demonstrates how to extend default user store managers by implementing a new user store, with comprehensive examples and project structure.
+
 !!! note "Do you want to create a custom user store that only has few enabled methods? Follow the steps given below:"
     1.  Sign in to the WSO2 API management console.
     2.  Click **Add** under User Stores.

en/docs/api-security/key-management/third-party-key-managers/configure-keycloak-connector.md

@@ -116,8 +116,8 @@ Follow the instructions given below to configure Keycloak as a third-party Key M
           <tr class="even">
             <td>Issuer</td>
             <td>The issuer that consumes or validates the access tokens
-            </br> e.g., https://localhost:8443/auth/realms/master</br>
-               http://localhost:8080/auth/realm</td>
+            </br> e.g., https://localhost:8443/realms/master</br>
+               http://localhost:8080/realm</td>
           <td>Mandatory</td>
           </tr>
           <tr class="odd">
@@ -128,16 +128,16 @@ Follow the instructions given below to configure Keycloak as a third-party Key M
           <tr class="even">
             <td>Client Registration Endpoint </td>
             <td>The endpoint to verify the identity and obtain profile information of the end-user based on the authentication performed by an authorization server.</br>
-            e.g., https://localhost:8443/auth/realms/master/clients-registrations/openid-connect
+            e.g., https://localhost:8443/realms/master/clients-registrations/openid-connect
             </td>
             <td>Mandatory</td>
           </tr>
           <tr class="odd">
             <td>Introspection Endpoint</td>
             <td>The endpoint that allows authorized protected resources to query the authorization server to determine the set of metadata for a given token that was presented to them by an OAuth client.
             </br> e.g., 
-            http://localhost:8080/auth/realms/master/protocol/openid-connect/token/introspect </br>
-               https://localhost:8443/auth/realms/master/protocol/openid-connect/token/introspect
+            http://localhost:8080/realms/master/protocol/openid-connect/token/introspect </br>
+               https://localhost:8443/realms/master/protocol/openid-connect/token/introspect
             </td>
             <td>Mandatory</td>
           </tr>
@@ -146,8 +146,8 @@ Follow the instructions given below to configure Keycloak as a third-party Key M
             <td>The endpoint that issues the access tokens.
             </br>
             e.g.,
-            http://localhost:8080/auth/realms/master/protocol/openid-connect/token</br>
-            https://localhost:8443/auth/realms/master/protocol/openid-connect/token
+            http://localhost:8080/realms/master/protocol/openid-connect/token</br>
+            https://localhost:8443/realms/master/protocol/openid-connect/token
             </td>
             <td>Mandatory</td>
           </tr>
@@ -274,7 +274,7 @@ Follow the instructions given below to configure Keycloak as a third-party Key M
             If this option is used to validate the tokens it is mandatory to add a Token Handling Option.
                 For the Okta it should be <b>JWT</b> and it is required to specify a claim mapping as a unique identifier.
             </br>e.g.,; Claim Key : iss
-            </br>Claim Value : https://localhost:8443/auth/realms/master </td>
+            </br>Claim Value : https://localhost:8443/realms/master </td>
             <td>Optional</td>
           </tr>
           <tr class="odd">