Workday Custom Attributes

Workday Provisioning


Okta can import users and groupsGroups allow you to organize your end users and the apps they can access. Assigning apps to large sets of end users is made easier with groups. from Workday through its standard API. Three types of imports are supported:

The optimal configuration of these import types can ensure optimal data accuracy and timeliness of data moving from Workday to Okta. They should be configured with consideration for the features and limitations of each import type.

Okta supports two typical scenarios: Import from Workday and Workday­driven IT Provisioning, as described below:


Before configuring provisioning in Okta, you need to do the following:




What versions of the Workday API are currently supported?

Okta supports v15 and v29 of the Workday API.

Are custom attributes supported?

Yes, we pull custom attributes in all of the imports. If you are not seeing a custom attribute, check the custom report in Workday with JSON endpoint and validate that the data is there.

What are the performance load that can be supported in a Workday as a Master implementation? How many users can be imported in a full import/incremental import?

Currently we passed 150k users in our scale testing. We continue to move forward towards 500k.

Are there technical limitations to integrating Okta with Workday?

We cannot determine changes on custom attributes for incremental imports if they do not have a transaction log tied to them, but if there are base attribute changes, we will pull in the custom attributes too.

Are there limitations when provisioning/de-provisioning users using custom attributes?

No, the user works the same with or without the custom attributes.

Are there limitations with a real time sync versus an import?

RTS requires a business process to be setup in Workday for each event you want to trigger.