<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content

Convert Social Provider Accounts to Okta-Sourced

API Access Management
Okta Classic Engine
Okta Identity Engine

Overview

Converting user accounts from a social Identity Provider (IdP) to Okta-sourced enables the management of credentials for users that originated from social providers. This conversion simplifies the registration process for end users when utilizing social logins for new user registrations. Administrators can perform this conversion through the Okta Admin Console or via the Okta Application Programming Interface (API).

Applies To

  • Okta Identity Engine (OIE)
  • Okta Classic Engine
  • Social Logins
  • Identity Providers (IdPs)
  • Application Programming Interface (API)

Solution

How is a social provider account converted to Okta-sourced via the Okta Admin Console?

Locate the user account in the Okta Admin Console and initiate a password reset to convert the account to Okta-sourced.

  1. Navigate to Directory > People and locate the desired user account.
  2. Click Reset or Remove Password.

Reset or Remove Password

  1. Select Send a reset password email.
Send a reset password email
4. Okta sends a password reset email to the end user. The end user can reset the password via email, or an administrator can create a temporary password. Creating a temporary password requires the end user to change the password during the next login.
 

How is a social provider account converted to Okta-sourced via the Okta API?

Execute Okta API calls to reset the user password, reactivate the user, and exchange the activation token to complete the conversion process.

  1. Call the API endpoint /api/v1/users/{{userID}}/lifecycle/reset_password?sendEmail=false to transition the user to the PROVISIONED state and set Okta as the credential provider.
    • NOTE: Setting sendEmail=true prompts Okta to send the Password Reset by Admin email template.
  2. Call the API endpoint /api/v1/users/{{userID}}/lifecycle/reactivate?sendEmail=true.
    • Okta sends the User Activation email template because the user is in a provisioned state.
  3. Either template includes an activation token that the application exchanges for a state token, allowing the configuration of a new password through /api/v1/authn/credentials/reset_password.

NOTE: If the user details indicate that a different source, such as Active Directory, sources the profile, the administrator must unlink the user from the Identity Provider. Unlink the user in the Okta Admin Console by selecting More Actions for the user and disconnecting the account from the Identity Provider, or utilize the Okta API to unlink the user.

 

Related References

Loading
Okta Support - Convert Social Provider Accounts to Okta-Sourced