@PrathamChoreria It looks like your target SCIM server is rejecting the pagination request because the connector is sending startIndex 9001 on the next page call, but the server enforces that pagination must always begin from startIndex 1
Possibly it’s going like this:
-
The SailPoint SCIM 2.0 connector uses index-based pagination — it increments
startIndexby thepageSizeafter each page (1 → 1001 → 2001 → … → 9001). -
Your target server does not support arbitrary startIndex values and requires pagination to always start from index 1 (likely using cursor-based or token-based pagination internally).
-
After successfully pulling all 8,511 accounts across 9 pages (pageSize 1000), the connector requests page 10 starting at index 9001, and the server rejects it with a 400 error.
Could you please try below config changes as mentioned in the connector guide:
Enable Non-compliant Server mode — In your application config, enable the Non-compliant Server? checkbox (or add <entry key="scim2NonCompliant" value="true"/> in the Debug page). This tells the connector to relax SCIM 2.0 strict compliance and can change how it handles responses
Try connector-level partitioning — Instead of relying on sequential pagination across all 8,511 accounts, use the partitionFilterMap to split the aggregation into smaller filtered chunks that each stay within the server’s pagination limits
References:
- Similar issue with AWS identity Center, see if the resolution mentioned over there could help you: AWS Identity Center Application Onboarding using SCIM Connector - IdentityIQ (IIQ) / IIQ Discussion and Questions - SailPoint Developer Community