This article clarifies how to configure attribute-level sourcing for an Okta user profile. This process is sometimes required to populate the Okta profile with an attribute from a specific application, as per the documentation on attribute-level sourcing.

• Lifecycle Management
• Universal Directory
• Attribute Level Sourcing

To complete attribute-level sourcing, the following tasks must be completed:

1. Make the application the profile source by following these steps:

   1. See Make an app the profile source.

   2. Optionally, enter the application name in the Search field.

   3. Click the application name in the list of applications.

   4. Click the Provisioning tab.

   5. Select To Okta in the Settings list.

   6. Scroll to Profile & Lifecycle Sourcing, click Edit, and select the Allow <app> to source Okta users check box.

   7. Click OK in the Enable Profile Sourcing dialog box if it appears.

   8. Optionally, select what should happen to the user when they are deactivated in the app:

      1. Do Nothing: Prevents activity in the app from controlling the user life cycle. This still allows profile source control of attributes and mappings.

      2. Deactivate: This default setting allows the user to be automatically deactivated when deactivated in the target app.

      3. Suspend: This setting allows the user to be automatically suspended when deactivated in the target app.

   9. Optionally, select what should happen to a user when they are reactivated in the app:

      1. Reactivate suspended Okta users: Allows an admin to choose if a suspended Okta user should be reactivated when they have been reactivated in the app.

      2. Reactivate deactivated Okta users: Allows an admin to choose if a deactivated Okta user should be reactivated when they have been reactivated in the app.

   10. Click Save.
       
       

2. Define the attribute profile source by following these steps:

   1. See Define the attribute profile source.

   2. When utilizing attribute-level sourcing, the profile source for each attribute can be defined.

   3. In the Admin Console, go to Directory > Profile Editor.

   4. Optionally, select Okta, Apps, Directories, or Identity Providers in the Filters list to filter the list of apps.

   5. Click Profile for the app, directory, or identity provider. (the name of the application).

   6. Optionally, select All, Base, or Custom in the Filters list to filter the attribute list.

   7. Click the information button in the right pane corresponding to the attribute intended for editing.

   8. Select one of these options in the Source priority list:

      1. Inherit from profile source: Default. Select this option to make the profile source the attribute source.

      2. Inherit from Okta: Select this option to make Okta the attribute source.

      3. Override profile source: Select this option and then select a profile source to override the default profile source and make another profile source the attribute source. This option does not disable the app as a profile source.

   9. Click Save Attribute.
      
      

3. Map profile attributes by following these steps:

   1. See Map profile attributes.

   2. In the Admin Console, go to Directory > Profile Editor.

   3. Click Mappings for the app and select Configure User mappings if a list appears.

   4. Select the App to Okta User tab in the User Profile Mappings dialog box.

   5. Map attributes by scrolling through the attribute mappings and ensuring that the required attributes in the target are mapped. The Okta or app user profile indicates which are required.

   6. Use the drop-down to add attributes, or use expressions to add attributes with concatenated or transformed values.

   7. Optionally, preview the mapping for a user.

   8. Click Save Mappings and Apply updates now.