AWS Identity Center Application Onboarding using SCIM Connector

Hello,

We have a requirement to onboard AWS IAM Identity Center to SailPoint IIQ, and we are leveraging the SCIM 2.0 Connector for this integration.

We have successfully onboarded the application and established connectivity. However, we are facing an issue during account and group aggregation.

Issue:

During account and group aggregation, IIQ retrieves a maximum of 100 users and 100 groups. It does not retrieve any records beyond this limit.

We have already configured the pageSize entry key in the application XML, following the same approach we used for other SCIM 2.0 connector integrations. However, this configuration does not resolve the issue, and aggregation continues to retrieve only 100 records.

How do we solve this issue?

Hi Balaji,

Which version of IIQ are you integrating with?

We are using SailPoint IIQ 8.5p1

Hello,

We faced a similar pagination issue during our AWS IAM Identity Center (AWS IDC) application onboarding in SailPoint IIQ.

What we found was that the SailPoint IIQ SCIM 2.0 Connector supports index-based pagination, whereas AWS IAM Identity Center expects and supports cursor-based pagination. Due to this difference in pagination mechanisms, we were unable to retrieve more than 100 users and groups during aggregation.

To overcome this limitation, we moved away from the SCIM 2.0 Connector and implemented the integration using the Web Services Connector.

The Web Services Connector provides greater flexibility and allows customization through Before Operation and After Operation rules. We leveraged these rules to handle the cursor-based pagination required by AWS IAM Identity Center and successfully overcome the aggregation limitation.

Our recommendation for onboarding AWS IAM Identity Center into SailPoint IIQ would be either:

  1. Use the out-of-the-box AWS IAM Identity Center Connector, if it meets your requirements.
  2. Use the Web Services Connector as an alternative to the SCIM 2.0 Connector.

In our experience, the Web Services Connector is a suitable alternative to the SCIM 2.0 Connector, as it provides the flexibility to implement the required SCIM API operations, pagination logic, and other integration capabilities through custom configurations and rules.

Hope this helps!

@BalajiChandrasekaran I would agree with @vamgada. Web Services Connector is the proven workaround and gives you full flexibility over pagination, auth, and attribute mapping. se Before/After Operation rules to handle cursor-based pagination against the AWS IDC SCIM endpoints (/Users, /Groups). Refer to the SailPoint Web Services Connector Guide for setup details. Do let us know if you need any help around there.