The following question can help narrow down the integration options available for web applications. You can learn more about the integration methods in the Explore section of this website.

This flowchart assumes that:

  1. the application will be integrated directly with the federation infrastructure instead of using an access gateway like PingAccess
  2. the source code for the web application is available (if not, PingAccess may be able to support this scenario)
Integration Option Scenario
Integrate directly with application / platform Application supports a federated security protocol such as SAML or WS-Federation (for example Microsoft SharePoint or Microsoft .NET) PingFederate and PingOne can be used to manage federation connection to partners.
PingFederate Web Server Integration Kits If the application server is IIS or Apache.
PingFederate Language Integration Kits (Java, .NET, PHP) Application is either Java, .NET or PHP. Especially if there is no direct communication between PingFederate and the application.
PingFederate Agentless Integration Kit Any code-based language that can make HTTP calls. Note: This kit requires direct connectivity between the application and PingFederate.
PingOne Application Provider Services Application is cloud-based or there are requirements that no software or libraries are to be used.
Native protocol support Application requires authentication and API authorization. OpenID Connect can be used to authenticate a user to an application client as well as provide an OAuth 2.0 access token use to secure API requests. Note: PingFederate can perform token translation allowing one token to be exchanged for another (i.e. a SAML assertion to be exchanged for an OAuth access token)
Note: In all cases, the Agentless Integration Kit and PingOne APS can be used to integrate an application with the Ping infrastructure quickly and simply.