I’m trying to integrate Salesforce with SailPoint using REST APIs. There are many different Salesforce endpoints available, and I’m a bit confused about which ones should be used for the integration.
If anyone has integrated Salesforce via REST API before, could you please share which endpoints you used?
Hello Sandy,
Welcome to the SailPoint Developer Community
Out of curiosity, is there a reason you are going with the Web Services connector? There’s already a SailPoint-built Salesforce connector that handles accounts, Profiles, Roles, Permission Sets, Permission Set Groups, Public Groups, and Queues natively. The Account Attributes page shows the full schema you would get out of the box.
In this Salesforce app, when creating a user, they’re adding a code and dates in the UI. This code is not required initially, but in some cases it becomes required later. They usually don’t know the code at the time of user creation, so they add it afterwards.
Got it. Are those code & date values stored directly on the Salesforce User object as custom fields, or are they on a separate custom object or related record in Salesforce?
If they are User object custom fields, you may not need the Web Services connector. The Salesforce connector supports custom User attributes for both aggregation and update, as long as the exact Salesforce API field names (with the __c suffix) are added to the account schema. You could keep them optional at create time and push the values later when they’re known.
If those values live on a different Salesforce object, Web Services with the Salesforce REST API may be the right direction.
I forgot to mention another case. When the user leaves the organization, we need to disable the account right. They don’t directly disable the user account, they need to reassign the user’s current assignments to a new user until the their replacement comes. Until a new replacement comes they’ll hold the account, and after reassigning all the assignments they’ll disable the acount