How do I defederate and refederate users?
You can defederate and refederate your federated users to increase their security by re-encrypting their vault.
About this task: To defederate and refederate your users, perform the following instructions:
- Defederate your federated users in the LastPass new Admin Console.
- Refederate your users.
- Perform one of the following set of instructions depending on your federation service:
- For Azure AD, Okta, Google Workspaces, PingOne or OneLogin: Users selected for federated login must log in to re-encrypt their vault.
- For AD FS or PingFederate: Migrate your selected users in the LastPass AD Connector.
- Check federated user statuses.
Step #1: Defederate your federated users in the LastPass new Admin Console
About this task:
Attention: The "Reset master password" option only becomes available after the selected user has logged out and logged back in using the LastPass browser extension (as login via the LastPass website at https://lastpass.com will not activate the "Reset master password" option for the admin). For more information about the encryption process, view What is the encryption process when a super admin resets a master password?
Review important information.
Reset the user's master password (as a Super Admin).
Results: You have de-federated your selected user.
What to do next: In case of a company wide refederation, update the company-wide K1 by performing one of the following set of instructions based on your selected provider:
Step #2: Refederate your users
Results: Your selected users are now marked for conversion.
Step #3: Perform one of the following set of instructions depending on your federation service
- For Azure AD, Okta, Google Workspaces, PingOne or OneLogin: Users selected for federated login must log in to re-encrypt their vault.
- For AD FS or PingFederate: Migrate your selected users in the LastPass AD Connector.
Users selected for federated login must log in to re-encrypt their vault with their Azure AD, Okta, Google Workspace, PingOne, or OneLogin
About this task: Users selected for conversion in
Step #2 above and with the
Selected status must log in to LastPass to re-encrypt their vault with their Azure AD, Okta, Google Workspace, PingOne, or OneLogin account, as follows:
- The user logs in with their existing username and master password via the LastPass browser extension only.
- Upon logging in to LastPass, the user is redirected to their Azure AD, Okta, Google Workspace, PingOne, or OneLogin (Identity Provider) sign in page where they must sign in with their Active Directory account for their Identity Provider.
- A progress bar is displayed to indicate that the user's LastPass vault is being re-encrypted with their Azure AD, Okta, Google Workspace, PingOne, or OneLogin account.
- Once complete, the user must log in again (using the LastPass web browser extension).
- The user is redirected to their company's federated login page (Identity Provider sign-in page), where they can finish signing in to LastPass using their Azure AD, Okta, Google Workspace, PingOne, or OneLogin account credentials.
Results: The user's LastPass account is now activated to use federated login, and they will continue to use their Azure AD, Okta, Google Workspace, PingOne, or OneLogin account credentials to access their LastPass vault. The newly converted federated login user(s) must use their Azure AD, Okta, Google Workspace, PingOne, or OneLogin account to sign in to LastPass going forward.
Migrate your selected users in the LastPass AD Connector for AD FS or PingFederate
Step #4: Check federated user statuses in new Admin Console
You can return to the new Admin Console to oversee the progress of your federated user migration by viewing federated statuses.
Results: Once all of your users have been migrated, your newly federated users will receive an email containing instructions on how they can log in using their federated account.
What to do next:
- To see your end user's experience, please see Federated login experience for LastPass Business users.
- For additional help with troubleshooting, please view the following articles: