Merge pull request #5599 from HasiniSama/minor-bugs

Fix minor documentation bugs - Outdated Asgardeo image, typo in SSO flow docs, and add MaxUserNameListLength config to docs

Author: HasiniSama

en/asgardeo/docs/assets/img/guides/organization/manage-organizations/sign-in-with-sso.png

@@ -326,4 +326,25 @@ pooling for LDAPS connections at the time of starting your server:
     -Dcom.sun.jndi.ldap.connect.pool.protocol=ssl
     ```
 
-4.  Start the server.
+4.  Start the server.
+
+## SCIM2 roles pagination
+
+When retrieving roles from the SCIM2/Roles endpoint, WSO2 Identity Server returns all users assigned to each role by default. For roles containing many users, this can lead to performance bottlenecks and block processing threads.
+
+To optimize performance and prevent thread blocking issues, configure the max users returned per role.
+
+```toml
+[pagination]
+max_users_list_per_role = <NUMBER_OF_USERS>
+```
+
+**Configuration details:**
+
+- **Default value**: 1000 users per role (when not configured)
+- **Lowest value**: 1000 users (values below 1000 automatically default to 1000)
+- **Scope**: Applies to all roles, including the built-in `everyone` role
+- **Database dependency**: Adjust this value based on your database performance capabilities
+
+!!! tip
+    Check database performance when roles have many users. Start with the default value and adjust based on your environment's capacity.

en/identity-server/6.1.0/docs/deploy/performance/performance-tuning-recommendations.md

@@ -235,4 +235,25 @@ Connection pooling does not apply to LDAPS connections (SSL-enabled LDAP connect
     -Dcom.sun.jndi.ldap.connect.pool.protocol=ssl
     ```
 
-4. Start the server.
+4. Start the server.
+
+## SCIM2 roles pagination
+
+When retrieving roles from the SCIM2/Roles endpoint, WSO2 Identity Server returns all users assigned to each role by default. For roles containing many users, this can lead to performance bottlenecks and block processing threads.
+
+To optimize performance and prevent thread blocking issues, configure the max users returned per role.
+
+```toml
+[pagination]
+max_users_list_per_role = <NUMBER_OF_USERS>
+```
+
+**Configuration details:**
+
+- **Default value**: 1000 users per role (when not configured)
+- **Lowest value**: 1000 users (values below 1000 automatically default to 1000)
+- **Scope**: Applies to all roles, including the built-in `everyone` role
+- **Database dependency**: Adjust this value based on your database performance capabilities
+
+!!! tip
+    Check database performance when roles have many users. Start with the default value and adjust based on your environment's capacity.

en/identity-server/7.0.0/docs/deploy/performance/performance-tuning-recommendations.md

@@ -235,4 +235,25 @@ Connection pooling does not apply to LDAPS connections (SSL-enabled LDAP connect
     -Dcom.sun.jndi.ldap.connect.pool.protocol=ssl
     ```
 
-4. Start the server.
+4. Start the server.
+
+## SCIM2 roles pagination
+
+When retrieving roles from the SCIM2/Roles endpoint, WSO2 Identity Server returns all users assigned to each role by default. For roles containing many users, this can lead to performance bottlenecks and block processing threads.
+
+To optimize performance and prevent thread blocking issues, configure the max users returned per role.
+
+```toml
+[pagination]
+max_users_list_per_role = <NUMBER_OF_USERS>
+```
+
+**Configuration details:**
+
+- **Default value**: 1000 users per role (when not configured)
+- **Lowest value**: 1000 users (values below 1000 automatically default to 1000)
+- **Scope**: Applies to all roles, including the built-in `everyone` role
+- **Database dependency**: Adjust this value based on your database performance capabilities
+
+!!! tip
+    Check database performance when roles have many users. Start with the default value and adjust based on your environment's capacity.

en/identity-server/7.1.0/docs/deploy/performance/performance-tuning-recommendations.md

@@ -235,4 +235,25 @@ Connection pooling does not apply to LDAPS connections (SSL-enabled LDAP connect
     -Dcom.sun.jndi.ldap.connect.pool.protocol=ssl
     ```
 
-4. Start the server.
+4. Start the server.
+
+## SCIM2 roles pagination
+
+When retrieving roles from the SCIM2/Roles endpoint, WSO2 Identity Server returns all users assigned to each role by default. For roles containing many users, this can lead to performance bottlenecks and block processing threads.
+
+To optimize performance and prevent thread blocking issues, configure the max users returned per role.
+
+```toml
+[pagination]
+max_users_list_per_role = <NUMBER_OF_USERS>
+```
+
+**Configuration details:**
+
+- **Default value**: 1000 users per role (when not configured)
+- **Lowest value**: 1000 users (values below 1000 automatically default to 1000)
+- **Scope**: Applies to all roles, including the built-in `everyone` role
+- **Database dependency**: Adjust this value based on your database performance capabilities
+
+!!! tip
+    Check database performance when roles have many users. Start with the default value and adjust based on your environment's capacity.

en/identity-server/next/docs/deploy/performance/performance-tuning-recommendations.md

@@ -541,7 +541,11 @@ Follow the steps below to see how organization login works for a user in the **H
 
 3. Click **Sign In with SSO** to specify the organization to which you are signing in.
 
+{% if product_name == "WSO2 Identity Server" and is_version > "7.1.0" %}
+4. Enter the **Organization Handle** of the organization and click **Submit**.
+{% else %}
 4. Enter **Happy Tails** as the organization name and click **Submit**.
+{% endif %}
 
     ![Sign in with SSO]({{base_path}}/assets/img/guides/organization/manage-organizations/sign-in-with-sso.png){: width="400" style="display: block; margin: 0; border: 0.3px solid lightgrey;"}