# 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. Legacy Ping Identity users who are not on PingOne should view our [Ping Identity documentation](https://docs.keeper.io/en/sso-connect-cloud/identity-provider-setup/ping-identity-keeper).
{% endhint %}

<figure><img src="https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MB_i6vKdtG6Z2n6zWgJ%2Fuploads%2F8GQRNyOkEjsIbcusWY5H%2FPingOne.jpg?alt=media&#x26;token=648e9f7e-c1be-4a61-9d0d-03f7ed596bdc" alt=""><figcaption></figcaption></figure>

### PingOne

Login to the PingOne portal at <https://admin.pingone.com/>.

![Login to PingOne](https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MB_i6vKdtG6Z2n6zWgJ%2F-MjUImi1PNhzRb4DWeTi%2F-MjUWB6c681jvuOUVqrT%2FScreen%20Shot%202021-09-13%20at%206.25.25%20AM.png?alt=media\&token=f263ddaa-f84c-414a-975b-796493a77f77)

From the **PingOne** console menu, select **Applications >** **Application Catalog**

Search "**Keeper**" and click on the **"Keeper Password Manager - Cloud SSO"** link to add the **Keeper Password Manager** application

<figure><img src="https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MB_i6vKdtG6Z2n6zWgJ%2Fuploads%2FDXz5CRXpDJ5mxhOvSa8G%2FKeeper_Password_Mgr_setup.png?alt=media&#x26;token=bfdd4ef0-42cd-471a-bfce-8430a6660c89" alt=""><figcaption></figcaption></figure>

Click **Setup** to proceed to the next step

<figure><img src="https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MB_i6vKdtG6Z2n6zWgJ%2Fuploads%2FWBTd89umkUAxgkzB24cL%2FKPM_Setup2.png?alt=media&#x26;token=b02239a0-9eb9-46e0-9356-f720b7adfcd8" alt=""><figcaption></figcaption></figure>

Click **"Continue to Next Step"**

<figure><img src="https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MB_i6vKdtG6Z2n6zWgJ%2Fuploads%2FKjgarSOYnfDukuWLgT7X%2FKPM_NextStep.png?alt=media&#x26;token=938ed593-995c-427a-a4e0-ce4268d83ebf" alt=""><figcaption></figcaption></figure>

From the **Keeper Admin Console**, view the PingOne SSO Connect Cloud entry and click **Export Metadata** and save it in a safe location for future use. Also click **Export SP Cert** and save it in a safe location for future use.

<figure><img src="https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MB_i6vKdtG6Z2n6zWgJ%2Fuploads%2FfMSGoW3HA5j7eEsRgFiZ%2FAdminConsole_metadata.png?alt=media&#x26;token=6434085b-44d4-4fa5-bda2-5e8619608b66" alt=""><figcaption></figcaption></figure>

From the PingOne Admin Console, click **Select File** next to "Upload Metadata" and browse to the saved metadata file from the **Keeper Admin Console**. This should populate the "ACS URL" and "Entity ID" fields with the proper datapoints.

Click on **Choose File** next to "Primary Verification Certificate" and browse to the saved `.crt` file from the **Keeper Admin Console.** Click on the checkbox next to "Encrypt Assertion" and then click **Choose File** next to "Encryption Certificate". Browse to the same saved `.crt` file from the **Keeper Admin Console.**

Validate the certificate and click **"Continue to Next Step".**

<figure><img src="https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MB_i6vKdtG6Z2n6zWgJ%2Fuploads%2Fu840FroomhVaatvFdJBW%2FKPM_Metadata.png?alt=media&#x26;token=8825e0fb-1460-4546-b93e-25716816b4a8" alt=""><figcaption></figcaption></figure>

Enter the appropriate values associated with each attribute (see below image) and click **Continue to Next Step**

<figure><img src="https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MB_i6vKdtG6Z2n6zWgJ%2Fuploads%2FcFNKeVl2wrMTsuD4tISg%2FKPM_DefaultAttributes.png?alt=media&#x26;token=ec63b645-3990-41aa-b72a-73eefd2f333d" alt=""><figcaption></figcaption></figure>

Modify the **Name** to appropriately match the Configuration Name of the SSO node from the **Keeper Admin Console**. Click **Continue to Next Step**

<figure><img src="https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MB_i6vKdtG6Z2n6zWgJ%2Fuploads%2FHjKQRwM0lp9uhXvKeJZ5%2FKPM_Name.png?alt=media&#x26;token=db5e0dfc-5445-47b8-aa9f-3e7667eb0d9f" alt=""><figcaption></figcaption></figure>

You may choose to add PingOne user groups to your application. Click **Add** next to the group or groups you would like to add and click **Continue to Next Step**.

{% hint style="info" %}
PingOne users will have access to Keeper Password Manager by default. Assigning groups to Keeper Password Manager restricts access to only those groups.
{% endhint %}

<figure><img src="https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MB_i6vKdtG6Z2n6zWgJ%2Fuploads%2FLgBSdicH1UYZ3uaLNKmN%2FKPM_Groups.png?alt=media&#x26;token=b9153e70-9b6d-4e58-972e-ef422aa581fd" alt=""><figcaption></figcaption></figure>

Click **Download** next to "SAML Metadata" and save the `.xml` file to a safe location.

<figure><img src="https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MB_i6vKdtG6Z2n6zWgJ%2Fuploads%2FQ7zstJEqBuuAxDeay0we%2FKPM_DownloadMetadata.png?alt=media&#x26;token=77cab031-cbc0-4dc8-95f9-13ea2db73cfd" alt=""><figcaption></figcaption></figure>

Click **Finish** to complete the application setup wizard.

On the **Edit Configuration** screen of the Keeper SSO Connect Cloud provisioning in the **Keeper Admin Console,** select **PingOne** as the **IDP Type.**

<figure><img src="https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MB_i6vKdtG6Z2n6zWgJ%2Fuploads%2FlaLFqmdgvq28PHRKEBDf%2FAdminConsole_IdP.png?alt=media&#x26;token=fcbf089e-38cd-4049-b53e-0b3aaed4093a" alt=""><figcaption></figcaption></figure>

Upload the SAML Metadata file downloaded in the previous step into the Keeper SSO Connect interface by browsing to or dragging and dropping the file into the **SAML Metadata** section.

<figure><img src="https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MB_i6vKdtG6Z2n6zWgJ%2Fuploads%2FfO6Ch0q7epW2kCbRkJuQ%2Fimage.png?alt=media&#x26;token=bad6c2b4-92a5-4443-b874-3008e2a8789f" alt=""><figcaption><p>Upload PingOne Metadata to Keeper</p></figcaption></figure>

The PingOne Keeper SSO Connect Cloud™ entry will now show as **Active**. \\

<figure><img src="https://2503956294-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MB_i6vKdtG6Z2n6zWgJ%2Fuploads%2FhOKPte6oCEi9UaFEgANL%2Fimage.png?alt=media&#x26;token=96dfa6c6-e99a-4dfb-93c7-a468292a2cf9" alt=""><figcaption><p>View Active Keeper SSO Connect Entry</p></figcaption></figure>

Your PingOne Keeper SSO Connect Cloud™ setup is 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://app.gitbook.com/s/-LO5CAzpxoaEquZJBpYz/domain-reservation).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.keeper.io/en/sso-connect-cloud/identity-provider-setup/pingone.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
