Workday TerminationDate Attribute Fails to Synchronize to Okta
Last Updated:
Overview
When a user termination date updates in Workday, the synchronization process to Okta fails, causing user access issues. This occurs because Workday only returns the termination date attribute via the API when the date matches the current date. Resolve this issue by setting termination dates to the current date in Workday and ensuring Okta imports occur after the attribute updates.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Workday
- Attributes
Cause
Workday returns the termination date attribute in the API response only when it matches the current date. If the termination date occurs in the past, Workday deactivates the user before the attribute update reaches Okta. If the termination date occurs in the future, Workday omits the attribute from the API response, preventing Okta from detecting impending terminations.
Solution
How is the Workday termination date synchronized to Okta?
Configure Workday termination dates and Okta import schedules to ensure accurate attribute synchronization.
- Set termination dates in Workday to the current date to enable real-time synchronization with Okta.
- Avoid setting termination dates in the past unless intended.
- Schedule Okta imports to occur after Workday updates the termination date attribute to capture the changes.
- Contact Workday support to determine if mapping the termination date attribute to a different field is supported as an alternative solution.
