How to Fix Workday Import with Confirm New User Action Error "Property <propertyname> is required"

When running the Workday Import job (or any App import job with 'Auto Confirm New User' creation enabled) with Auto Confirm New User enabled under Okta Admin Console > Applications > Applications > Workday > Provisioning > To Okta, under User Creation & Matching > Confirm New Users section, some auto/manual confirm new Okta user creation has failed due to error:

 Property <propertyname> is required

Sample of import configuration: 
 

Sample of Okta new user creation failure during Workday Import > Auto Confirm New User task:

• Workday
• Okta Integration Network
• User Lifecycle Management 

As the error stated, this is normally caused by a required Okta user attribute being detected with a null value, which caused the new Okta user creation job to fail as part of the auto/manual confirm new user Workday import action.

For the default Okta user type, there are, by default, 4 base Okta user attributes (Okta username, firstName, lastName, email) that are required user attributes. For full details, please read the KB article: Okta Base User Required Attributes. In addition to that, Okta also allows the creation of a custom Okta user type and adding a custom user attribute to the default Okta user profile/custom Okta user profile, where the Okta Admin user may configure whether the newly created custom user attribute is a required Okta user attribute(s) field. 

To avoid errors during the Workday import > Auto Confirm New User step, please ensure that the attribute level source (whether it is Okta, Workday, or any other profile master configured in the Okta org instance) always has the required custom attribute value set.

We recommended the following steps for troubleshooting to remediate the failed Okta user creation task error: 

1. Please navigate to Okta Admin Console > Directory > Profile Editor > under the Okta user profile (default/custom) and verify whether there is one or more base/custom Okta user attributes called '<propertyname>' (as listed in the System Event log error message) which was as a required property.

   If yes, please also verify the currently attribute level master set for this missing required custom Okta user attribute. For full details, please read the KB article: Attribute Level Mastering / Attribute Level Sourcing. 

2. If it should be set from Workday import (where Workday as Profile Sourcing is being configured), then please further verify and confirm what the current Workday to Okta mapping in Profile Editor for the missing required Okta user attribute field and verify whether the problematic sourced Workday worker user profile does have the non-null attribute value being set and being properly imported from Workday into Okta. 

3. Once the above are completed, please rerun the Workday import again. Make sure this time the new Okta user is being created properly without previous errors.