PingOne

Considerations after integrating or migrating a PingID account into a PingOne environment

After migrating your PingID account to a PingOne environment, consider the following post-requisites.

Check for user accounts that didn’t migrate successfully

When migrating a PingID account to a PingOne environment the process can complete even if a small number of the PingID accounts fail to migrate successfully. After migration is complete, you should check the PingID administrative activity report to see whether any user accounts failed to migrate. The report includes the total number of failed accounts as well as an entry identifying the username for each failed account.

Contact Ping Identity for instructions on how to resolve issues with the migration of specific user accounts.

Enabling users to manage their devices using MyAccount when using an external IdP (such as PingFederate)

When using an external IdP, to enable your users to manage their devices using MyAccount, you’ll need to do the following tasks in PingOne:

  1. Add the IdP as an external IdP. Learn more in External IdPs.

  2. Add the external IdP to an authentication policy. Learn more in Adding an authentication policy.

  3. In the PingOne Self-Service - My Account application Policies tab, add the authentication policy that you created in the previous step.

  4. Enable MyAccount. Learn more in Self Service.

Enable administrators to manage user devices

To provide administrators the permissions necessary to manage user devices from the PingOne admin portal, do the following:

  1. In the Administrators environment in PingOne, manually create one or more Admin accounts.

  2. Assign the admin accounts the permissions necessary to manage user devices for the PingOne environment with which you integrated the PingID account.