Manage user profiles
Universal Directory (UD) is a platform that delivers rich user profiles and fine-grained control over how attributes flow between applications. This enhancement makes it easier for organizations to create and maintain a single source of truth for its users, enabling new authentication and provisioning scenarios.With UD and Profile Editor, you can:
These capabilities enable you to do the following:
Warning: Universal Directory and the accompanying Profile Editor features are very powerful options. The alteration of profiles and mappings can have unintended effects in downstream apps — please be cautious when making such changes. Note that when an attribute in a user's profile triggers an update, Okta updates the user's entire profile in the application.
Using Universal Directory
The following explains UD features, configuration of features, and use-cases. Topics include
Profiles (Okta End User and App User)
UD introduces profiles, representations of user accounts. In particular, UD supports two types of profiles: the Okta End User profile, and the App user profile. The two profile types are used to store rich attributes in Okta and move rich attributes from Okta to 3rd-party apps.
Use the Profile Editor to view or modify these profiles: Directory >Profile Editor.
The Okta user profile represents a user in Okta (an Okta account) and is comprised of two parts: base attributes and custom attributes. Okta users can either be end users, people who use Okta to access the applications they use each day, or users, which is used to refer to Okta administrators who use Okta to administer their org's environment.
View the Okta end user profile
To view the Okta end user profile:
Okta has defined 31 default base attributes for all users in an org. These base attributes are generally fixed and cannot be modified or removed. There are two exceptions: First Name and Last Name. These two attributes can be marked as required or optional for Okta-mastered users only. To import users with blank First Name or Last Name attributes, you must first mark the attributes as optional in Okta, otherwise the import will fail.
Make First Name, Last Name optional
To make First Name or Last Name attributes optional:
If you wish to add additional attributes to the user profile, you can add them as custom attributes.
You can only add attributes to the directory profile if they are already in the directory, so Okta first does a schema discovery step to populate the attribute picker. For Okta to discover the attribute, it must be added to an object within the User object hierarchy in the directory: user object, a parent object, or an auxiliary object.
The agent takes a few seconds to execute the schema discovery. When it’s done you’ll get a list of the attributes that Okta has the permissions to discover in the directory.
You can extend an Okta User profile by adding an attribute to the custom portion of the profile. Base attributes cannot be altered.
Remove Custom Attributes from a user profile
You can remove an attribute to the custom portion of the profile. Base attributes cannot be altered.
App User Profile
An app user profile represents a user in a 3rd-party application, directory, or identity provider (IdP). The app user profile lists the 3rd-party's attributes that Okta can read and write to (read-only for IdP). This profile is used to control the attributes that Okta pushes to an app or the attributes imported from an app into Okta.
Similar to Okta user profiles, app profiles have both base attributes and custom attributes. Custom attributes for app user profiles differ from those for Okta user profiles. Whereas Okta user profiles can be extended with any custom attribute, app user profiles can only be extended with attributes from a predefined list that Okta dynamically generates. Okta generates the list of attributes by querying the 3rd-party application or directory for supported attributes.
Note: Active Directory users, look here for details on Using Custom Attributes with Active Directory.
Profile mappings allow administrators to precisely control the attributes exchanged during provisioning processes. The two chief use-cases that UD facilitates are
In the first use-case (App to Okta), organizations typically use a source-of-truth app such as a directory or human resources system. Some organizations might have several sources of truth. Mappings define how attributes from these various sources are imported into the Okta user profile.
The diagram below illustrates the first use case. In the example, Active Directory (AD) and Workday supply the Okta user profile with attributes (AD provides FirstName and LastName; Workday provides Boss). The diagram illustrates the mapping of givenName and sn to FirstName and LastName (from AD to Okta), and it shows the mapping from managerUserName to Boss (from Workday to Okta).
In the second use-case (Okta to App), organizations wish to propagate the data in Okta to other applications to provision accounts and update accounts with rich data. This is possible if the Okta user profile has rich attributes and the app in Okta is UD-upgraded.
The following diagram illustrates the second use-case. In the example, Okta sends four attributes to Google. The diagram shows the mappings of four Okta user profile attributes to four Google App user profile attributes.
Using the Profile Mapping Tab
To create a mapping between the Okta user profile and the app user profile:
To remove a mapping, simply delete the entry from the field and then click Save mapping.
The details above describe how to map attributes that flow from one source to another without modification. For example, a first name of "John" imported from Google gets stored as "John" in Okta. However, if you wish to modify attributes before storing them in Okta or sending them to apps, you can do this with expressions within the mappings.
Expressions allow you to concatenate attributes, manipulate strings, convert data types, and more. Okta supports a subset of the Spring Expression Language (SpEL) functions. Find a comprehensive description of the supported functions under Okta Expression Language. All functions work in UD mappings.
Disclaimer: While some functions (namely string) work in other areas of the product (e.g., SAML 2.0 Template attributes and custom username formats), not all do.
Expressions are useful for maintaining data integrity and formats across apps. For example, you might wish to use an email prefix as a username, bulk replace an email suffix, or populate attributes based on a combination of existing ones (e.g., displayName = lastName, firstName).
To configure an expression, do the following:
Okta allows you to handle the most demanding username requirements. Constructing custom Okta user names or application user names with Okta's data and expression language is easy.
Example use cases:
The username override feature overrides a previously selected Okta username format or app username format (different per app). When username override is configured, the previously selected username formats no longer apply.
Username override can also be used with Selective Attribute Push to continuously update app user names as user profile information changes. For example, if a user gets assigned to an app with a username of email, and that email subsequently changes, Okta can automatically update the app username to the new email. Prior to this enhancement, an Okta admin had to manually change a user's app username by unassigning the user and reassigning him to the app. This enhancement applies to all apps and is not limited to only apps with provisioning capabilities.
Note: For a list of the characters supported in Okta email addresses, see here.
Configure Username Override
To override an Okta username, do the following:
To override an app username, do the following:
To keep the app username automatically updated, do the following:
Rich SAML Assertions and WS-Fed Claims
UD attributes can be sent in SAML assertions and WS-Fed claims. Apps can consume rich SAML assertions and WS-Fed claims to do the following:
Configure Rich SAML Assertions and WS-Fed Claims
Currently, only the App Integration Wizard, Template WS-Fed and Template SAML 2.0 can send UD data.
Note: The Template SAML 2.0 is deprecated.
To configure this: