Salesforce - SCIM Configuration - RSA Ready Implementation Guide
This article describes the configuration steps involved in integrating Salesforce with RSA Cloud Authentication service using SCIM. RSA Cloud Authentication Service will serve as the SCIM client with Salesforce acting as a SCIM server providing an endpoint for the SCIM client to connect.
Configure RSA Cloud Authentication Service as a SCIM Client
Perform these steps to configure RSA Cloud Authentication Service as a SCIM client.
Procedure
- Sign in to the RSA Cloud Administration Console.
- Navigate to Applications > Application Catalog and choose salesforce.com.
- On the Basic Information page, provide a name for the Salesforce app and an optional description.
- If an integration for Salesforce using SAML or OIDC is needed, refer to the articles listed in the Integration Configuration section of Salesforce - RSA Ready Implementation Guide. If only fulfillment is needed, proceed to the next step.
- Navigate to the Fulfillment page in the left pane.
- Enable the fulfillment service by using the toggle button and choose the Approver Type from: None, Manager, Application Owner, Manager, and Application Owner.
- In the Fulfillment Configuration Type drop-down list, choose SCIM Endpoint and enter the required details.
- Base URI: https:// <your-salesforce-instance>.salesforce.com/services/scim/v2
- API Key: The refresh token obtained from step 13 in the Salesforce configuration section.
- Groups Object ID: (From Salesforce: Users > Profiles. Click the profile that you want the provisioned user to have and copy the ID from the URL). For example: https:// <your-salesforce-instance>.salesforce.com/<Profile_ID>
Note: In Salesforce, profiles are an essential part of the system's security and access model. A profile defines a user's permissions, settings, and access to objects, fields, and records in Salesforce.
- Enable OAuth 2.0 and fill in the following details:
- OAuth 2.0 URL: https:// <your-salesforce-instance>.salesforce.com/services/oauth2/token
- Client ID: The consumer key obtained from step 9 in Salesforce configuration section.
- Client Secret: The consumer secret obtained from step 9 in the Salesforce configuration section.
- Click Save and Finish and publish the changes.
Configure Salesforce as a SCIM Server
Perform these steps to configure Salesforce as a SCIM server.
Procedure
- Sign in to Salesforce with an administrator account.
- On the Setup menu, navigate to Platform Tools > Apps > App Manager.
- In the main pane, choose New Connected App.
Note: Connected App will be the SCIM client that will gain access to Salesforce’s SCIM API with credentials obtained. - On the Create a Connected App page, choose Create a Connected App.
- In the Basic Information section, fill in the App Name, API Name, and Contact Email for the New Connected App.
- Under API (Enable OAuth Settings) section:
- Select Enable OAuth Settings.
- Callback URL: https://login.salesforce.com/
- Under Selected OAuth Scopes, add:
- Manage user data via APIs (api)
- Perform requests at any time (refresh_token, offline_access)
- Clear the Require Proof Key for Code Exchange (PKCE) Extension for Supported Authorization Flows checkbox.
- Click Continue to save and confirm creating the connected app.
- On the newly created connected app settings page, under the API (Enable OAuth Settings) section, click Manage Consumer Details.
- Take note of the Consumer Key (Client ID) and Consumer Secret (Client Secret).
- Use the following URL which contacts the authorization server of Salesforce to obtain the authorization code:
https://<your-salesforce-instance>.salesforce.com/services/oauth2/authorize?response_type=code&client_id=<Consumer_Key>&redirect_uri=<Callback_URL>&scope=api+refresh_token- Replace <your-salesforce-instance>with your own instance from salesforce. You can obtain the instance URL by clicking on your profile icon on the page and the URL is displayed under your name.
- Replace the <Consumer_Key> with the one in the previous step.
- Replace <Callback_URL> with the URL configured in Salesforce.
- You will be prompted by the consent to allow access and for the permissions that were earlier identified by the Scope in the OAuth2.0 Settings. Click Allow.
- In the URL of your browser, the authorization code can be seen after the part “code=”. Take note of this code.
- Exchange the authorization code obtained from the previous step from the Authorization Server of Salesforce to get the access token and a refresh token by running the following command after replacing the relevant values.
curl -X POST -H "Content-Type: application/x-www-form-urlencoded" \ -d
"grant_type=authorization_code" \ -d
"code=<Authorization_Code>" \ -d
"client_id=<Consumer_Key>" \ -d
"client_secret=<Consumer_Secret>" \ -d
"redirect_uri=<Callback_URL>" \ https://<your-salesforce-instance>.salesforce.com/services/oauth2/token - Store both tokens securely. The refresh token will be used to obtain the Access Token automatically without having the Admin manually change the Access Token when it expires in RSA Cloud Authentication Service.
The configuration is complete.
Return to Salesforce - RSA Ready Implementation Guide.
Related Articles
UPDATE: RSA Via LG Integrations with Salesforce Using TLS 1.0 Encryption Protocol 38Number of Views Salesforce Experience Cloud - SAML My Page SSO Configuration - RSA Ready Implementation Guide 21Number of Views Salesforce SSO Device Activation Changes – Impact on RSA Integrations 28Number of Views Root CA certificate is required for activation error when importing a custom certificate signed by a known CA into Operati… 507Number of Views User changes his mobile device in RSA Cloud Authentication Service 126Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.9 Release Notes (January 2026) An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?