# Auth0
{% hint style="success" %}
Please complete the steps in the [Admin Console Configuration](https://docs.keeper.io/en/sso-connect-cloud/admin-console-configuration) section first.
{% endhint %}
### Auth0 SSO Configuration
Login to the Admin section of the Auth0 portal.
Select the **Applications** tab and click **Create Application**. Choose **Regular Web Applications**.
Next, go to the **Addons** tab and click **SAML2 WEB APP**.
On the Settings page that comes up next, you will need the “Assertion Consumer Service (ACS) Endpoint” that comes from the Keeper Admin Console.
**Example Assertion Consumer Service (ACS) Endpoint:**\
\*\*
This value can be found under the SSO Connect Cloud configuration as part of the Service Provider information, as seen below:
Paste the Assertion Consumer Service (ACS) Endpoint into the Application Callback URL field in the Auth0 screen.
Next, remove the sample JSON in the SAML2 Web App editor window, and replace with the following:
```
{
"audience": "https://keepersecurity.eu/api/rest/sso/saml/XXXXX",
"mappings": {
"email": "Email",
"given_name": "First",
"family_name": "Last"
},
"createUpnClaim": false,
"passthroughClaimsWithNoMapping": false,
"mapUnknownClaimsAsIs": false,
"mapIdentities": false,
"nameIdentifierFormat": "urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress",
"nameIdentifierProbes": [
"http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress"
]
}
```
The value for “audience” is the Entity ID. This can also be found under the SSO Connect Cloud configuration as part of the Service Provider information:
Once you've added the Entity ID, you can click the **Debug** button to verify there are no formatting issues.
Next, scroll down to the bottom of the SAML2 Web App window and click **Save**.
Save changes made to the SAML2 Web App settings
Next, click on the **Usage** tab and download the Identity Provider Metadata file.
Download IdP metadata
On the Keeper side, edit the SSO configuration and select GENERIC as the IDP Type. You can upload the metadata.xml file into the Keeper SSO Connect interface by browsing to or dragging and dropping the file into the Setup screen:
#### 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.
{% hint style="warning" %}
An admin can not move themselves to the SSO enabled node. It requires another admin to perform this action.
{% endhint %}
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.
Initially select 'Enterprise SSO Login'
Once the user has authenticated with SSO, they only need to use their email address moving forward to initiate SSO authentication. They won't have to enter the Enterprise Domain.
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](https://docs.keeper.io/enterprise-guide/domain-reservation).
