How to Map Attributes from Workday to an Okta User Profile
Last Updated:
Overview
In the Universal Directory (UD) Profile Editor, the base profile that Okta imports from Workday consists of 20 attributes. Some of the attribute mappings from the Workday user to the Okta user exist by default, but others need to be created manually.
The table below contains the recommended attribute mappings for typical use cases that can map 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 |
Applies To
- Workday
- Okta User Profile
- Attribute Mapping
Solution
When Workday is configured to write to Active Directory(AD) and UD is enabled, the Okta admin must manually map some attributes between the Workday app user profile and the Okta user profile, as well as the Okta user profile and the AD user profile. This allows attributes to flow from Workday to Okta and then to AD.
The attribute mapping can be done by logging into the Admin Dashboard and navigating to Directory > Profile Sources > Workday > Map profile from Workday to Okta.
