This article provides instructions on how to bring missing attributes into the Salesforce integration.
The Salesforce integration missing the attributes is in the list below:
|
Title |
title |
|---|---|
|
Nickname |
communityNickname |
|
Cell |
mobilePhone |
|
Phone |
phone |
|
Street |
street |
|
City |
city |
|
State/Province |
state |
|
Zip/Postal Code |
postalCode |
|
Employee Number |
employeeNumber |
|
Company Name |
companyName |
|
Division |
division |
|
Department |
department |
|
Manager |
managerId |
|
Feature Licenses |
featureLicenses |
|
Role |
role |
|
Permission Sets |
salesforceGroups |
|
Public Groups |
publicGroups |
- Okta Classic Engine
- Salesforce
- Provisioning
A common cause is that an administrator mistakenly deleted an attribute. When an attempt is made to add the attribute back through the Pick Schema Attributes, it does not appear.
If there are multiple Salesforce integrations and one of them is missing, for example, the attribute public groups, previously the attribute was displayed, but currently, it is not showing, the first step is to make sure that the API connector is working as intended and there are no restrictions.
Follow the steps or watch the video below to determine if the Service account was previously used to establish proper communication between Okta and Salesforce and vice versa.
- Create an administrator account in Salesforce.
- In the Admin Console, go to Applications > Applications.
- In the search field, enter Salesforce and click Salesforce.com.
- Click the Provisioning tab and click Configure API Integration.
- Select the Enable API integration check box.
- If the instance is configured to use OAuth, enter the OAuth Consumer Key and OAuth Consumer Secret, then click Authentication with Salesforce.com. For more details, see Configure OAuth and REST integration.
- To avoid breaking the integration, use a dedicated API account to connect Okta to Salesforce: Do not use the Salesforce admin account, even if the account has the Global Admin role.
- Do not enable delegated authentication in Salesforce for the API user specified here.
- Optional: Select the Allow Pushing Null Values check box to allow null values to be pushed from Okta to Salesforce.
- Optional. Click Test API Credentials to test the API integration.
- Click Save.
After the API connector is working as intended and the attribute is still not showing in the list, schedule a maintenance window outside working hours and follow the steps :
- Uncheck the Create Users, Update User Attribute, Deactivate Users, and Sync Password.
- Test the API credentials to see that provisioning is working properly.
- Disable (deactivate) the integration, refresh the page, and re-enable (re-activate) the integration.
- Test the API credentials to see that provisioning is working properly.
- Check to see if this brings back the attribute.
If this procedure is still not bringing the attributes in, please open a support case.
