This article explains an issue with Okta when performing a scheduled full or incremental import from Workday (or another application with scheduled import functionality). During the initial import, a user was found but did not match an existing Okta user. However, in the next import job run, a matching Okta user was identified. In subsequent scheduled import jobs, the system recognized the user as an exact match based on the User creation & Matching condition but did not auto-confirm the match, even though the Auto-Confirm Exact Match setting was enabled.
Alternatively, manual imports can be continued to resolve this issue. However, this article will discuss an alternate option to avoid the manual import remedy action.
- Any Application import (Active Directory, Workday, BambooHR, Google Workspace, etc.)
- Imports
- Early Access (EA)
This issue occurs because user matching conditions are not being re-evaluated during subsequent scheduled incremental/full imports but are being re-evaluated during subsequent manual imports by default.
Okta Admins can now enable a self-service Early Access (EA) feature called Force rematch imported users to Okta users directly from the Okta Admin Console > Settings > Features > Early Access page.
Then, allow the subsequent scheduled import job to run as normal, and it will force reevaluated imported users to rematch against Okta users upon all subsequent scheduled import jobs.
Okta Admin user may verify in the Okta System Log that the suggested self-service EA system feature has been enabled using the below Okta system log search query:
eventType eq "system.feature.enable" and target.id eq "ENG_FORCE_REMATCH_FOR_IMPORTS"
Alternatively, manual imports can be continued to resolve this issue.
