SecureAuth
How to configure Keeper SSO Connect Cloud with SecureAuth for seamless and secure SAML 2.0 authentication.
Please complete the steps in the Admin Console Configuration section first.
![](https://docs.keeper.io/~gitbook/image?url=https%3A%2F%2F2503956294-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MB_i6vKdtG6Z2n6zWgJ%252Fuploads%252FnutWt2CPLh9j8FmUdbJu%252FSecureAuth.jpg%3Falt%3Dmedia%26token%3D4e4965b9-4541-4888-a326-930c8a397222&width=768&dpr=4&quality=100&sign=b6470d51&sv=1)
SecureAuth can be configured using the same instructions in the Other SAML 2.0 Providers section. Please follow that guide in order to set up the SecureAuth environment.
For reference, use the SecureAuth guide located here:
A few additional important items to note regarding SecureAuth:
Ensure that "By Post" is selected in the Connection Type section:
![](https://docs.keeper.io/~gitbook/image?url=https%3A%2F%2F2503956294-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MB_i6vKdtG6Z2n6zWgJ%252Fuploads%252FSOHcE1kc3YwJhv7w0qrG%252FScreen%2520Shot%25202022-07-28%2520at%25204.54.28%2520PM.png%3Falt%3Dmedia%26token%3Dcd6829d8-3c43-4886-80cf-b11288a00aaa&width=768&dpr=4&quality=100&sign=90a0faa7&sv=1)
Ensure to select "Sign SAML Assertion" and "Sign SAML Message".
Ensure the Entity ID of the IdP metadata matches the SAML response from SecureAuth.
Move existing users/initial admin to SSO authentication
Users created in the root node (top level) will need to be migrated to the sub node that the SSO integration was configured on. If users remain in the root node, they will be prompted for the master password when accessing the vault and/or admin console.
An admin can not move themselves to the SSO enabled node. It requires another admin to perform this action.
After the user is moved to the SSO enabled node, they need to log into the Keeper vault initially by selecting the "Enterprise SSO" pull down and inputting in the Enterprise Domain configured on the SSO integration. The user may get prompted to confirm by entering in the master password.
![](https://docs.keeper.io/~gitbook/image?url=https%3A%2F%2F2503956294-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MB_i6vKdtG6Z2n6zWgJ%252Fuploads%252FfFPNzWDvSwH48ebLJOeY%252FSSO_Login.png%3Falt%3Dmedia%26token%3Df7bc0249-986d-427d-9746-0e7873ff7840&width=768&dpr=4&quality=100&sign=be6b680a&sv=1)
Once the user has authenticated with SSO, they only need to use their email address moving forward to initiate SSO authentication.
If typing in the email address and clicking Next does not route the user to the desired SSO, ensure that just-in-time provisioning is enabled in the Keeper SSO configuration and ensure that your email domain is reserved by Keeper. More information regarding routing and domain reservation can be found here.
Last updated