This article clarifies whether an existing attribute within a user profile can be used to populate attributes in other user profiles, respectively, whether one Okta user profile can act as the source of truth for specific attributes within other user profiles.

• User Lifecycle Management
• Universal Directory
• Profile Source

Understanding the Limitation

While Okta offers robust user profile management features, there is currently no functionality for admins to directly map attributes from one user profile to another. This means a scenario where one user's profile acts as the sole source for populating specific fields in other user profiles cannot be created.

Alternative Solutions

Although direct attribute mapping between user profiles is not available, Okta provides alternative solutions to streamline user data management:

• Universal Directory: Okta's Universal Directory acts as a central hub for user identities. Applications can be configured to pull user data from this directory, ensuring consistency across connected apps. By maintaining a single source of truth (typically the primary Okta User Profile) within the Universal Directory, attribute updates in one profile will reflect in connected applications.
• SCIM Provisioning: If using SCIM (System for Cross-domain Identity Management) for user provisioning, Okta's pre-configured SCIM templates can be leveraged. These templates map source attributes (from the existing user identity system) to corresponding attributes in Okta user profiles.
• Custom User Attributes: Custom user attributes can be created for scenarios requiring unique data points not captured by standard Okta attributes. These custom attributes can then be populated during user creation or through directory integrations.

Related References

• About profile sourcing