Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

AWS SSO SCIM API pagination for methods

9

I'm using the AWS Single Sign-On SCIM implementation API for and integration of AWS SSO with Google workspace, the project is here: https://github.com/slashdevops/idp-scim-sync/ and I also contributed in the AWS original one: https://github.com/awslabs/ssosync which is not active anymore.

The integration I did is working fine until you don't have more than 50 users of 50 groups in the AWS SSO service. That is because you have several limitations on the AWS SSO SCIM API implementation, described here

so, the question is:

When do you be able to allow the pagination for the ListGroups and ListUsers endpoints?

this API have some time already published and we are waiting so long for this feature.

Topics
Security, Identity, & Compliance
Tags
AWS IAM Identity Center
Language
English
asked 4 years ago902 views
1 Answer
0

Hello christiangda, apologies for taking so long to answer this. I understand your concern regarding the current limitations, especially when dealing with more than 50 users or 50 groups in AWS SSO. Regarding the timeline for allowing pagination for these endpoints, I don't have specific information about when this feature will be implemented. AWS continuously works on improving its services based on customer feedback, but I can't provide details on future release dates or specific feature implementations.

However, I can offer some suggestions and information that might be helpful:

Stay updated: Keep an eye on the AWS SSO documentation (see link below) and release notes for any updates regarding pagination support for these endpoints. Link ->> https://repost.aws/questions/QURqsaKxH9SqWYsBJ9UDdAPg/aws-sso-scim-api-listgroups-members

AWS Support: If this feature is critical for your use case, consider contacting AWS Support. They may be able to provide more information or escalate your request internally.

Workarounds: In the meantime, you might need to implement workarounds in your integration to handle the current limitations. This could involve making multiple API calls and combining the results on your end.

Feedback: Use the AWS feedback channels to express your need for this feature. Customer feedback is valuable for prioritizing improvements and new features.

Alternative approaches: Consider exploring other AWS identity and access management solutions that might better suit your needs for larger-scale integrations.

Best practices: Ensure you're following AWS SSO best practices for large-scale deployments, which might help mitigate some of the challenges you're facing.

Hopefully this provides you with some guidance.

Thank you for using AWS!

Brian

AWS
answered 10 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content