Implementing Pagination for Large Sub-Attributes of SCIM Resources

[HasiniSama]

Is your suggestion related to an experience ? Please describe. The current SCIM specification does not address the challenges associated with managing large sub-attributes within SCIM resources. We are currently encountering performance issues when dealing with resources that have large lists of associated entities, such as:

• Roles API: Handling roles with a large number of associated users
• Groups API: Managing groups with a large number of members.
• Users API: Retrieving users associated with multiple groups or roles.

Although the SCIM Working Group (WG) has acknowledged this issue, and a draft solution (expired) has been proposed, it has not yet been adopted as a standard. Therefore, we propose to develop our own solution to implement sub-attribute pagination based on our specific requirements.

Describe the improvement We propose implementing sub-attribute pagination within our SCIM APIs. By doing so, we aim to improve API performance and scalability, particularly when dealing with large lists of sub-attributes.

Additional context

• If the SCIM specification is updated later and conflicts with our implementation, changing the API afterward would be problematic. Therefore, we need to be cautious and design this solution to minimize the need for future adjustments.

[HasiniSama]

The following issues were also observed in the UI.

• When assigning users to a role, only a limited number of users can be assigned.
• Can not search users from the name

The behavior is the same when assigning groups to a role.