We've been trying to get a SCIM connection working (v9.0.01), but are having issues being able to integrate any target object type outside of Users and Groups. This is specifically for non-Starling Salesforce SCIM. We had issues with the Groups' schema, so had to use a manual version that resolved the specific uniqueness issue. ServiceProviderConfigs.json ResourceTypes.json Schemas.json When we validate the Resource Types, it clearly shows the end points, but they don't then show in the target schema and they can't be created. Has anyone managed to get additional target object types working for SCIM?

Your ResourceType json does not match your Schema json properly. According to your ResourceType.json the /Entitlements endpoint holds entries of "urn:salesforce:schemas:extension:1.0:Entitlement" but your schema only defines "urn:salesforce:schemas:extension:2.0:Entitlement" (1.0 vs. 2.0). The same goes for /Roles. ResourceTypes points to "urn:salesforce:schemas:extension:1.0:Role"; schema defines "urn:salesforce:schemas:extension:2.0:Role" (1.0 vs 2.0). Also, your schema json contains endpoint attributes. This is odd, because according to RFC they are neither defined nor expected there.

SCIM and extension object types

Ben over 1 year ago

We've been trying to get a SCIM connection working (v9.0.01), but are having issues being able to integrate any target object type outside of Users and Groups.

This is specifically for non-Starling Salesforce SCIM. We had issues with the Groups' schema, so had to use a manual version that resolved the specific uniqueness issue.

When we validate the Resource Types, it clearly shows the end points, but they don't then show in the target schema and they can't be created.

Has anyone managed to get additional target object types working for SCIM?

Top Replies

Andreas Finsterbusch over 1 year ago in reply to Ben +2 verified

Your ResourceType json does not match your Schema json properly.

According to your ResourceType.json the /Entitlements endpoint holds entries of "urn:salesforce:schemas:extension:1.0:Entitlement" but…

0 Andreas Finsterbusch over 1 year ago

Your links produce a Access denied. Might be there is something odd with your json files, that prevent the proper discovery.
On the other hand, did you finalize your sync project or shrink the schema? This will remove unused schema objects. Do you see the missing endpoints after using "update schema"?
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
0 Ben over 1 year ago in reply to Andreas Finsterbusch

Those are just copies of the JSON files, was using advanced feature to use file system local copies as had to fix the Schemas.json from the Saleforce supplied document.

Alternate ResourceTypes.json and Schemas.json

No, shrink schema is not the issue.
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
+1 Andreas Finsterbusch over 1 year ago in reply to Ben

Your ResourceType json does not match your Schema json properly.

According to your ResourceType.json the /Entitlements endpoint holds entries of "urn:salesforce:schemas:extension:1.0:Entitlement" but your schema only defines "urn:salesforce:schemas:extension:2.0:Entitlement" (1.0 vs. 2.0).

The same goes for /Roles. ResourceTypes points to "urn:salesforce:schemas:extension:1.0:Role"; schema defines "urn:salesforce:schemas:extension:2.0:Role" (1.0 vs 2.0).

Also, your schema json contains endpoint attributes. This is odd, because according to RFC they are neither defined nor expected there.
Cancel
Up +2 Down

Reply

Verify Answer

Reject Answer

Cancel
0 Ben over 1 year ago in reply to Andreas Finsterbusch

Thank you. That resolved it besides Saleforce swearing black and blue there is nothing wrong with their documents as plenty of clients are using their SCIM. Go figure.
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
0 OneIdentity_Dev over 1 year ago in reply to Ben
Hi Ben

I am also facing similar issue connecting to SAP BTP using SCIM.

Connecting SAP BTP to OneIdentity using SCIM Connector

It is happening due to version mismatch One1M (v2.0) and SAP BTP (v1.0) and no upgrade is possible for SAP BTP

We are thinking of using below json files to override the default one's

ResourceTypes.json

Schemas.json

Could you please once again attach the dummy .json files so that we can refer and develop with v1.0 ?
Cancel
Up 0 Down

Reply

Verify Answer

Cancel