SCIM SAAS connector - Account aggregation fails while entitlement aggregation succeeds

Identity Security Cloud (ISC) ISC Discussion and Questions
, ,
1

We have configured a SCIM service. Entitlement aggregation is working fine. But account aggregation fails with “404 Not found”

The /Users endpoint works in Postman.

Here is the status of the working/non working URLS
Working URLs
https://xxxxxx.com/api/v1/scim/ServiceProviderConfig
https://xxxxxx.com/api/v1/scim/ResourceTypes
https://xxxxxx.com/api/v1/scim/Users
https://xxxxxx.com/api/v1/scim/Groups

Not Working URLs
https://xxxxxx.com/api/v1/scim/schemas
https://xxxxxx.com/api/v1/scim/schemas/User

Could the non working urls be a problem?

2

Hey @nileshnikalje!

The SCIM connector requires these endpoints as explained in the connector documentation. So yes, missing the /schemas endpoints is causing the issue.

  • The SailPoint SCIM 2.0 connector requires the following endpoints with valid response for Connector execution:
    • /ServiceProviderConfig
    • /ResourceTypes
    • /Schemas
    • /ResourceTypes/User
    • /Schemas/urn:ietf:params:scim:schemas:core:2.0:User

Depending on the configuration of the source API, you could either use the non-compliant settings to get the connection working, or you can build a Web Services connector to call the necessary endpoints (VA-based Web Services connector or SaaS Web Services Connector).

Please let me know if this helps answer your question!

  • Zach
1 Like
3

Thanks. It confirms the non-working behaviour of the SCIM SAAS connector