Testing

You can test the .NET Integration Kit using one of the sample applications bundled with this distribution.

Learn more about prerequisites, configuration, and running sample applications in Sample applications setup.

When setting up the sample applications, don’t import the data.zip configuration archive into a PingFederate instance that has an existing configuration you want to keep. Importing the archive overwrites your entire PingFederate configuration.

Testing IdP-initiated SSO

With both sample applications and PingFederate running, go to the following URL to start an IdP-initiated SSO flow:

https://localhost:9031/idp/startSSO.ping?PartnerSpId=localhost:default:entityId&IdpAdapterId=OTIdPJava

Or access the Idp application at https://localhost:5001 and click Single Sign On. The browser redirects to the IdP application’s login page. After authenticating, PingFederate processes the OpenToken, generates a SAML assertion, and redirects to the SP application, which displays the authenticated user’s attributes.

Testing SP-initiated SSO

Go to the SP application at https://localhost:5002 and click Single Sign On.

Or go directly to: https://localhost:9031/sp/startSSO.ping?PartnerIdpId=localhost:default:entityId&SpSessionAuthnAdapterId=OTSPJava

Testing single logout

From either test application’s home page, click Logout to initiate single logout (SLO). PingFederate propagates the logout to both applications and redirects the browser to the configured target resource upon completion.

To test local logout only, without triggering a PingFederate SLO, go to /LocalLogout on either application.