# Ping Identity (PingOne)

{% 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 %}

<figure><img src="https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MB_i6vKdtG6Z2n6zWgJ%2Fuploads%2FBuIyzAXh6aFiVuFVBBk6%2FPing.jpg?alt=media&#x26;token=536663b0-266d-4eac-af15-46b07ea2a05c" alt=""><figcaption></figcaption></figure>

### Ping Identity Configuration

Login to the Ping Identity portal.

<figure><img src="https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MB_i6vKdtG6Z2n6zWgJ%2Fuploads%2F3k0ri8MWL9H5z8JpEI6K%2FScreenshot%202025-11-13%20151316.png?alt=media&#x26;token=7920a12c-0fa7-44c8-82e4-a76c7917a17b" alt=""><figcaption></figcaption></figure>

In your existing Environment click **Manage Environment.**

<figure><img src="https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MB_i6vKdtG6Z2n6zWgJ%2Fuploads%2FoKnxjKF5jFmOVCvArXh1%2FScreenshot%202025-11-13%20152059.png?alt=media&#x26;token=aad01cf4-f6d0-4ae4-b7d8-dd1e1e2fd352" alt=""><figcaption></figcaption></figure>

![](https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MB_i6vKdtG6Z2n6zWgJ%2F-MjUImi1PNhzRb4DWeTi%2F-MjUWYaXZ6F6q9jZw2FN%2FScreen%20Shot%202021-09-13%20at%207.18.27%20AM.png?alt=media\&token=6e3054f0-9a50-4eb4-8951-fb824d06071f)

On the left, click **Applications** > **Application Catalog** > Search "**Keeper**" and select "**Keeper Password Manager**"

<figure><img src="https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MB_i6vKdtG6Z2n6zWgJ%2Fuploads%2FBiSY9JWupivs2yNb5ras%2FScreenshot%202025-11-13%20152526.png?alt=media&#x26;token=7c90201d-ce8f-4b93-9a39-3eeadc6c6645" alt=""><figcaption></figcaption></figure>

On the Application Details page, add the following data:

* Keeper Security Domain: **keepersecurity.com**
* Keeper Security Identifier: Can be found in the admin console under Entity ID **<https://keepersecurity.com/api/rest/sso/saml/\\><Identifier>**
  * Log in to the **Keeper Admin Console** at <https://keepersecurity.com/console/>.
  * In the **left panel**, go to **Admin** and select a **sub-node** (not the root).
  * Navigate to **Provisioning → Add Method → Single Sign-On with SSO Connect® Cloud**.
  * Enter a configuration name, add your domain, and click **Save**.
  * After the SSO configuration is created, click the **three-dot menu (⋮)** next to it and select **View** to display the **Entity ID**.
* Once that is complete we can save and move on to the next steps.

<figure><img src="https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MB_i6vKdtG6Z2n6zWgJ%2Fuploads%2FPAauqbH8RFK30IkLgI8m%2FScreenshot%202025-11-13%20153009.png?alt=media&#x26;token=7f0d5ac9-2282-448d-8da3-5d0ff72b5b86" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MB_i6vKdtG6Z2n6zWgJ%2Fuploads%2F8f6s0eGioFfsmjo80lQ7%2FScreenshot%202025-11-13%20153228.png?alt=media&#x26;token=a8023ea3-8e7f-4729-a200-ec7958db69a3" alt=""><figcaption></figcaption></figure>

Next, we can add the **Groups** who will be accessing the Keeper Application and click **Save.**

<figure><img src="https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MB_i6vKdtG6Z2n6zWgJ%2Fuploads%2FR8ffReYfXnZaBJcJDcoh%2FScreenshot%202025-11-13%20153327.png?alt=media&#x26;token=a4121432-6bf8-48e3-b79e-7dc2e905d4e3" alt=""><figcaption></figcaption></figure>

Click **Download Metadata** as we will upload this to Keeper in the next step.

* In attribute 1, type “**First**” in the Application Attribute column, select **First Name** in the Identity Bridge Attribute or Literal Value column, and check the Required button. Select the **Add new attribute** button.
* In attribute 2, type "**Last"** in the Application Attribute column, select **Last Name** in the Identity Bridge Attribute or Literal Value column, and check the Required button. Select the **Add new attribute** button.
* In attribute 3, type "**Email"** in the Application Attribute column, select **Email** in the Identity Bridge Attribute or Literal Value column, and check the Required button. Application Attributes: First, Last, Email must begin with a capital letter.

{% hint style="warning" %}
Application attribute names are case-sensitive. Ensure all attribute names use uppercase as shown in the examples. Using lowercase values may cause parsing errors during SSO setup.
{% endhint %}

<figure><img src="https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MB_i6vKdtG6Z2n6zWgJ%2Fuploads%2FmeabxPZxUDlub0itL6CL%2FScreenshot%202025-11-13%20161250.png?alt=media&#x26;token=a64be6e4-84e6-4fa2-8de0-824d025b1604" alt=""><figcaption></figcaption></figure>

\
\
On the Edit screen of the Keeper SSO Connect Cloud provisioning select "Generic" as the IDP Type and upload the saml2-metadata-idp xml file into the Keeper SSO Connect interface by browsing to or dragging and dropping the file into the Setup screen:

<figure><img src="https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MB_i6vKdtG6Z2n6zWgJ%2Fuploads%2F3yRUI6ZdbDTWC0PvVIXo%2FScreenshot%202025-11-13%20153756.png?alt=media&#x26;token=ef65ac70-cb7f-42f2-b520-21e193f51a08" alt=""><figcaption></figcaption></figure>

The Keeper Application should be added and enabled.

Your Keeper SSO Connect setup is now complete!

#### 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.

<figure><img src="https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MB_i6vKdtG6Z2n6zWgJ%2Fuploads%2FfFPNzWDvSwH48ebLJOeY%2FSSO_Login.png?alt=media&#x26;token=f7bc0249-986d-427d-9746-0e7873ff7840" alt=""><figcaption><p>Initially select 'Enterprise SSO Login'</p></figcaption></figure>

Once the user has authenticated with SSO, they only need to use their email address moving forward to initiate SSO authentication.

<figure><img src="https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MB_i6vKdtG6Z2n6zWgJ%2Fuploads%2FDrVwIHQiMQDtlxeJey0G%2Fvault_Login.PNG?alt=media&#x26;token=2e435451-c23e-41bd-91e2-8ec49a216c16" alt=""><figcaption></figcaption></figure>

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).
