Error in aggregating accounts for SCIM connector

Hi everyone,

I’m trying to onboard a new source with SCIM 2.0 connector and SCIM 2.0 SaaS connector - direct connection type.

SCIM 2.0 - Test Connection is successful and when I do discover schema in Account Schema section its throwing en error - org.json.JSONException: A JSONObject text must begin with ‘{’ at 1 [character 2 line 1]

SCIM 2.0 SaaS - Test connection is successful and when I run Account Aggregation its throwing java.lang.RuntimeException - java.lang.IllegalStateException: [ConnectorError] Maximum number of redirects exceeded

SCIM APIs are working as expected from Postman. Could you please let me know how to resolve this issue?

Thanks,
Abhijit

Hi @abhijit_shekki,
Could you share a little more relating to what you are connecting to - is it SCIM compliant?

The connector will use SCIM compliant endpoints to discover schema

You can use these endpoints to test

GET {{baseUrl}}/ServiceProviderConfig
GET {{baseUrl}}/ResourceTypes
GET {{baseUrl}}/Schemas/User
GET {{baseUrl}}/Schemas/User

Do these work in POSTMAN?

Hi @sk8er23 - Thanks for your reply.

In my case I’ve a baseUrl something like this – https://test.com/scim
Users API – https://test.com/scim/Users
Groups API – https://test.com/scim/Groups

And these work in POSTMAN.

These are all standard SCIM endpoints, if your SCIM server is compliant then it should have these. They will need to be functional for the Sailpoint SCIM connector to work as expected (attribute discovery for instance), otherwise you will need to develop a custom web services connector to work with your api.

Thanks for the explanation.

Now I’m able to successfully test the discover schema and aggregation with the SCIM 2.0 SaaS connector. However when I ran the Entitlement Aggregation, the members attribute of each groups is showing something like INCORRECT TRANSLATION FORMAT. I tried to change the type of the members attribute to string and multivalued but still its not working.

Can you please help?

Can you get some entitlements from POSTMAN and check if any have a special characters - this may be the reason for your error INCORRECT TRANSLATION FORMAT

I tried to fetch entitlements from Postman and I don’t see any special characters with respect to the entitlements details

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.