What are the limitations for LastPass users with federated login?
There are feature limitations that apply to LastPass Business users whose accounts are configured for federated login using AD FS, Azure AD, or Okta.
- Federated login works only via LastPass Browser Extension, LastPass Desktop Client and the LastPass Mobile Apps.
- LastPass Browser Extension: Chrome/Edge/Safari/IE/Opera/Firefox
- LastPass Desktop Client: LastPass for Windows Desktop, LastPass for macOS
- LastPass Mobile Apps: Android, iOS (iPhone/iPad)
- Not supported: Android Wearables/ Apple Watch
- LastPass Federated login does not work if the LastPass Desktop Clients or the LastPass Mobile Apps are managed via Microsoft MDM/Intune or other MDM solutions.
- Federated login does not work via web login including mobile browser
- No Offline access – The client side (web browser extension) must remain online in order to obtain the user's encryption key and unlock the user's LastPass Vault. For this reason, offline login is not available.
- No One-Time Password – This feature is not available as the Master Password comes from the user's Active Directory (AD FS, Azure AD, or Okta) environment.
- Limited Account recovery options – For federated users, the Master Password comes from the user's Active Directory environment. Therefore, password recovery can be done in either of the following ways:
- Password reset via the user's Active Directory user management
- Password reset using the "Permit super admins to reset Master Passwords" policy within LastPass, however, this will change the user's status from federated to non-federated – please see Reset a User's Master Password (Super Admin) for more information.
- No Multifactor Authentication enabled within LastPass – Multifactor Authentication must be set up at the Identity Service Provider level, not at the LastPass level. It must be disabled within the LastPass Admin Console (learn how here) and end user Account Settings (learn how here). If enabled within LastPass, it will result in federated users being unable to access their Vault.
- No Multifactor Authentication policies enforced within LastPass – You must disable all Multifactor Authentication policies in the LastPass Admin Console (learn how here) because this authentication occurs at the Identity Provider level. If even one Multifactor Authentication policy is enabled in LastPass, it will result in federated users being unable to access their Vault.
- Only Service Provider single sign-on (SSO) is supported – This means that you must always begin the login process from a LastPass component (e.g., web browser extension, mobile app, or desktop app) in order to be redirected to your organization's Identity Provider sign in page. Logging in via the LastPass website at https://lastpass.com/?ac=1 is not supported for federated users.
- About Linked Personal Accounts (for Azure AD or Okta federated users only) – Linked personal accounts must be verified on every new device that a federated AD FS, Azure AD, or Okta user will use for logging in to access their LastPass Vault.
- Other policy limitations – All policies related to Master Password Strength and/or Master Password Rules will not affect federated users if enforced, and should be disabled at all times for those users. Learn how to manage your policies.
Please note that if a user's status changes from federated to non-federated (e.g., due to a Master Password reset), the limitations listed above will be lifted but the user will still be required to adhere to company policies that have been applied to their LastPass Business account. However, you can convert these users back to a federated status again without the risk of data loss. Please see the instructions that apply to your federated login setup: