Import Active Directory users


There are several ways to import usersIn Okta literature, we generally refer to "users" as the people who serve as Okta administrators. When we refer to "end users" we are generally referring to the people who the administrators serve. That is, those who use Okta chiclets to access their apps, but have no administrative control. from Active Directory (AD) into Okta.

Some key terms to understand:

Activate/Activation — When users are imported from AD an Okta account is created for this user. The Okta account and the AD account are bound together via the confirmation process. Since an Okta account is created during this process the Okta account has to be activated before it can be used.

Assign and unassign — In the context of Okta, users imported from AD became assigned to the AD appAn abbreviation of application. Essentially, it is a web-based site used to perform any number of specific tasks, and requires authentication from end users by signing in. similar to any other app in Okta. When end usersIn Okta literature, we generally refer to "end users" as the people who have their own Okta home page (My Applications), using chiclets to authenticate into all of their apps. End users do not have any administrative control. When we refer to "users" we are generally referring to the individual(s) who have administrative control. are assigned to an app, they usually see the chiclet for the app on their Okta home page. AD users imported into Okta do not see an AD chiclet on their home page.

Import— This is the act of Okta reaching out to AD, asking for its users then bringing (importing) those users into Okta.

Match — When users are import form AD, Okta searches for an existing account in Okta based on the matching rules you have set. If it finds an account that matches the AD account it will match the users and confirm them: bind them together. If there is not a matching user, Okta creates a new user. For example: there is an AD account Jamesf, and in Okta there is an account named jamesf. Upon import Okta will see the AD jamesf and the Okta jamesf and match them. If there is no jamesf in Okta it will create one

Confirm match - This is the act of confirming the match. Some admins prefer to let this happen automatically, while others decide to manually match accounts as they come in. This is based on the confirmation settings you have chosen.





Next Steps

If you are configuring your Okta org and have just imported users for the first time, you will need to perform the following tasks:

Top