Map Attributes From Workday to an Okta User Profile
Last Updated:
Overview
In the Universal Directory (UD) Profile Editor, the base profile Okta imports from Workday includes 20 attributes. While some attribute mappings from the Workday user to the Okta user are available by default, administrators must manually map other attributes to ensure data flows correctly from Workday to Okta and then to Active Directory (AD).
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Workday
- Attribute Mapping
Solution
How are attributes mapped from Workday to an Okta user profile?
When an environment uses Workday to write to AD and enables UD, administrators must manually map specific attributes between the Workday application user profile and the Okta user profile, as well as between the Okta user profile and the AD user profile. This configuration allows attributes to flow seamlessly from Workday to Okta and then to AD.
Access the profile sources in the Okta Admin Console and select the Workday application to configure the attribute mappings.
- Navigate to Directory and select Profile Sources.
- Choose Workday.
- Select Map profile and configure the mappings from Workday to Okta.
What are the recommended attribute mappings?
Review the following table of recommended attribute mappings for typical use cases from Workday to Okta.
|
Workday |
Okta |
|---|---|
| appuser.accountType | userType |
| appuser.businessTitle | title |
| appuser.businessUnit | department |
| appuser.city | city |
| appuser.countryCode | countryCode |
| appuser.email | |
| appuser.employeeID | employeeNumber |
| appuser.firstName | firstName |
| appuser.lastName | lastName |
| appuser.location | locale |
| appuser.managerId | managerId |
| appuser.managerUserName | manager |
| appuser.mobilePhone | mobilePhone |
| appuser.postalCode | zipCode |
| appuser.secondEmail | secondEmail |
| appuser.state | state |
| appuser.streetAddress | streetAddress |
| appuser.supervisoryOrg | organization |
| appuser.workPhone | primaryPhone |
