{"id":285,"date":"2025-04-01T13:45:08","date_gmt":"2025-04-01T12:45:08","guid":{"rendered":"https:\/\/vtom.uk\/?page_id=285"},"modified":"2025-04-01T13:45:08","modified_gmt":"2025-04-01T12:45:08","slug":"okta-salesforce-provisioning","status":"publish","type":"page","link":"https:\/\/vtom.uk\/index.php\/okta-salesforce-provisioning\/","title":{"rendered":"Okta – Salesforce Provisioning"},"content":{"rendered":"\n

While the Okta and Salesforce documentation is comprehensive, while setting up and testing the integration, I found complications relating to missing attributes and problems with use of multiple groups for Salesforce Permissionsets and Profiles.<\/p>\n\n\n\n

Missing Attributes<\/strong>
By default the following attributes are not mapped to the Okta Integration Network Salesforce app, which must be used if using Okta for Salesforce user provisioning:
* Email Encoding (EmailEncodingKey)
* SAML Federation ID (FederationIdentifier)
* Locale (LocaleSidKey)
* Time Zone (TimeZoneSidKey)<\/p>\n\n\n\n

All of these are substantial for many Salesforce setups, so to add them, navigate from the Okta Admin Dashboard through Directory > Profile Editor. Search for the Salesforce App and select it, to bring up the Profile Editor. Select “Add Attribute”.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Select the missing attributes then select Save.
Navigate through the Okta Admin Dashboard to Applications then Application and select the Salesforce app. Select Provisioning and scroll down and the attributes will be available to assign values to:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Multiple Group Membership<\/strong>
Using Okta for Salesforce provisioning, the default settings cause a problem when more than one Salesforce PermissionSets, Profiles and PublicGroups are being used. This is documented on Okta’s KB: User Assigned to the Salesforce App through Multiple Groups only Inherit the Permission Sets from One Group<\/a><\/p>\n\n\n\n

The default behaviour will cause only the first group (in the Okta provisioning order) to be transmitted to Salesforce, however this is insufficient for most Salesforce configurations which use more than one group to logically separate users into permission sets and profiles, and users may well be in more than one group.<\/p>\n\n\n\n

Navigate from the Okta Admin Dashboard to Directory > Profile Editor. Search for the Salesforce app and select it.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

The profile editor will appear:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Scroll down and select the pencil next to “PermissionSets”:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Change “Use Group Priority” to “Combine values across groups” and select [Save Attribute]<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Repeat for other attributes that are managed through group membership, where it is possible for a user to be a member of multiple groups (e.g. “Public Groups”)<\/p>\n\n\n\n

<\/p>\n","protected":false},"excerpt":{"rendered":"

While the Okta and Salesforce documentation is comprehensive, while setting up and testing the integration, I found complications relating to missing attributes and problems with use of multiple groups for Salesforce Permissionsets and Profiles. Missing AttributesBy default the following attributes are not mapped to the Okta Integration Network Salesforce app, which must be used if … Continue reading Okta – Salesforce Provisioning<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-285","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/vtom.uk\/index.php\/wp-json\/wp\/v2\/pages\/285","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vtom.uk\/index.php\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/vtom.uk\/index.php\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/vtom.uk\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vtom.uk\/index.php\/wp-json\/wp\/v2\/comments?post=285"}],"version-history":[{"count":1,"href":"https:\/\/vtom.uk\/index.php\/wp-json\/wp\/v2\/pages\/285\/revisions"}],"predecessor-version":[{"id":297,"href":"https:\/\/vtom.uk\/index.php\/wp-json\/wp\/v2\/pages\/285\/revisions\/297"}],"wp:attachment":[{"href":"https:\/\/vtom.uk\/index.php\/wp-json\/wp\/v2\/media?parent=285"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}