This article details how to determine an Okta user's profile source.

• Reporting
• Administration
• Profile Source
• Okta Classic Engine

An Okta org may have several profile sources, and it may become necessary to identify each user's profile source. If such a need arises, however, there is no direct report that details an Okta user's profile source. Instead, this information must be reasonably inferred. For this, the User App Access report can provide much, if not all, of the required information.

1. Go to Directory > Profile Sources to find all Profile Sources and their numbered priority.

2. Go to Reports > Reports and create a User App Access report.

3. Use the following filters in the report: 

   • Application - Includes any of the profile source applications.
   • App assignment type - includes any of the "Individual" assignment types.
     • A user with an "Individual" assignment type in a profile source app means that the appuser profile was imported, versus a "Group" assignment type, which for profile sources means that the user was provisioned to the app from a provisioning group.
   • Okta user status - includes any having the "Active" status.
     • Deactivated users cannot have app assignments.

To determine the profile source of a user,  find the user in the exported report.

• If the user appears only once, that app is the profile source.
• If the user appears more than once, the app with the highest profile source priority will be the user's most likely profile source.
  • To verify, view the user's Okta profile page.
• If the user does not appear on the report, the user is Okta-sourced.

For example, An Org has three profile sources in order of priority:

1. Workday
2. AD domain1.local
3. AD domain2.local

Running the report provides the following results:

• User test1@example.com appears twice, once for Workday and once for Active Directory 2.
  • This user's profile source most likely is Workday.
• User test2@example.com appears once for domain1.local.
  • The user's profile source is domain1.local.
• User test3@example.com does not appear on the report.
  • The user's profile source is Okta.