PingFederate Server

Updating the PingOne for Enterprise identity repository

You can upload configuration changes to your connected PingOne for Enterprise account’s admin portal or disconnect from your PingOne for Enterprise account if needed.

About this task

After a managed service provider (SP) connection to PingOne for Enterprise admin portal is established, PingFederate include::partial$pf_rc_monitorsp1relatedconfigchanges.adoc[tags=pf_ph_pfMonitorsPingOneRelatedConfigChanges] to PingOne for Enterprise. When PingFederate detects such changes, the administrative console prompts you to decide whether to update PingOne for Enterprise or to disconnect from PingOne for Enterprise in a banner message.

Steps

  1. Go to System → External Systems → PingOne for Enterprise settings.

    Choose from:

    • To upload configuration changes to your PingOne for Enterprise account, click Update PingOne Identity Repository.

      This is applicable if you have made changes that you should propagate to your PingOne for Enterprise account.

      For example, you are about to set up a new SAML application on PingOne for Enterprise that requires a telephone number of the user. Because the current attribute contract in the managed SP connection does not include an attribute for telephone number, you extend the attribute with a new attribute, PrimaryTelephone. After the connection is saved, the administrative console prompts you to decide whether to update PingOne for Enterprise or to disconnect from PingOne for Enterprise. In this example, you should upload the new configuration to PingOne for Enterprise so that the new PrimaryTelephone attribute is made available when you set up the new SAML application in PingOne for Enterprise.

    • To disconnect PingFederate from your PingOne for Enterprise account, click Disconnect from PingOne.

      This is applicable if you have made changes that you should not propagate to your PingOne for Enterprise account.

      For instance, you have two PingFederate environments, testing and production. The production PingFederate server is configured with a managed SP connection to PingOne for Enterprise, but the PingFederate test server is not. You have just exported a configuration archive from the production server and imported it to the test server. As soon as the configuration archive is imported, the administrative console prompts you to decide whether to update PingOne for Enterprise or to disconnect from PingOne for Enterprise. In this example, you should disconnect the test server from PingOne for Enterprise so that nothing is uploaded to your PingOne for Enterprise account from the test server.