1. Start PingFederate.
  2. In a web browser, open the sample application:

    https://pf_host:pf_port/IdpSample

    If you deployed the application elsewhere, modify the host name accordingly. For help, see Advanced installation and configuration.

  3. On the IdP Application home page, click Local Login.
  4. On the Local Login page, sign on with the following credentials.

    Username: joe

    Password test

  5. Click Login.
    When you authenticate locally to the IdP sample application, no communication occurs between the application and PingFederate; the user authenticates using the local user store. No SSO use cases are invoked until PingFederate is called on the home page via the Single Sign-On button.
  6. If you customized your configuration by creating different SP connections or deploying the IdP application on a separate server, update the application configuration as shown in IdP sample application configuration reference.
  7. After logging on to the IdP sample application, theIdP Application home page appears again. In addition to SSO/SLO information and controls, this page now shows attributes that will be sent to the SP in the SAML assertion.

    The steps below describe how to test the basic SSO/SLO functionality of this page:

    1. Click Single Sign-On to begin IdP-initiated SSO to the SP sample application. A user session on the SP is created, and you are logged-in to the SP sample application. For more information, see Using the SP sample application.
    2. To demonstrate IdP-initiated SLO, return to this identity provider page by changing the browser location back to https://pf_host:pf_port/IdpSample. Then click Single Logout to initiate an SLO request to the SP. When the user session on the remote SP is destroyed, the local session is destroyed as well (clicking Single Sign-on here or on the SP application page redirects to the IdP logon page).
      Note: If you initiate SSO from the SP, the Single Logout button is operational and will also end both sessions. If you click Local Logout on this screen, the SP session is still in force; you can access the SP application directly in the browser and see the attributes passed in from the original SAML assertion.