.NET Integration Kit

Overview of the SSO flow

With the .NET Integration Kit, PingFederate exchanges user attributes with your .NET 8 application through an OpenToken.

The following figure shows a basic identity provider (IdP)-initiated single sign-on (SSO) scenario in which PingFederate federation servers using the .NET Integration Kit exist on both sides of the identity federation:

diagram of the .NET Integration Kit SSO flow

Description

  1. A user initiates an SSO transaction.

  2. The IdP application passes user attributes to the .NET 8 OpenToken Agent, which encrypts the data internally and generates an OpenToken.

  3. A request containing the OpenToken is redirected to the PingFederate IdP server.

  4. The PingFederate IdP server invokes the OpenToken IdP Adapter, which retrieves and decrypts the OpenToken, parses the user attributes, and uses them to generate a SAML assertion.

  5. The SAML assertion is sent to the SP site.

  6. The PingFederate SP server parses the SAML assertion and passes the user attributes to the OpenToken SP Adapter. The adapter encrypts the data internally and generates an OpenToken.

  7. A request containing the OpenToken is redirected to the SP application.

  8. The .NET 8 OpenToken Agent decrypts and parses the OpenToken, making the user attributes available to the SP Application.