Application "Import from CSV" Not Auto-Matching Users
Last Updated:
Overview
Before an application has provisioning set up, the only option under the Import tab is Import from CSV. This article will explain this import's behavior and why it does not auto-match imported users.
Applies To
- Lifecycle Management
- Application import
- User creation via import
Cause
Using the Import from CSV option from the application's Import tab (which is available only if provisioning is not configured or the application does not support normal provisioning) is similar to a normal import, but a CSV file containing the usernames of the users that should be imported to Okta is needed. The main procedure difference is that, for “Import from CSV,” no user matching or provisioning settings are applied to disabled users. The imported users will remain in the Import tab until manually confirmed.
Solution
It is an expected behavior for any user imported via Import from CSV not to be auto-confirmed or matched with an existing Okta user. Manual intervention is needed to confirm each one of them.
Upon confirmation, it is possible to expand the imported user, choose EXISTING Okta user I specify and match the user with an existing Okta account.
