Once a managed SP connection to PingOne® for Enterprise is established, PingFederate monitors configuration changes that may impact the connection, such as an update to the base URL or an import of a configuration archive that includes a managed SP connection to PingOne for Enterprise. When PingFederate detects such changes, the administrative console prompts you decide whether to update PingOne for Enterprise or to disconnect from PingOne for Enterprise in a banner message.

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

    Applicable if you have made changes that should be propagated 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. Once 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 becomes available when you set up the new SAML application in PingOne for Enterprise.

  • To disconnect PingFederate from your PingOne for Enterprise account, click PingOne for Enterprise Settings; then click Disconnect from PingOne on the PingOne for Enterprise Settings screen.

    Applicable if you have made changes that should not be propagated 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. The test PingFederate 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 will be uploaded to your PingOne for Enterprise account from the test server.