This integration uses a RESTful approach that doesn't require you to integrate agent software into your application. Instead, your application exchanges user-session attributes with PingFederate through direct HTTP calls to the adapter endpoints.

The Reference ID IdP Adapter can also redirect OAuth authorization consent requests to an external application, as described in External consent approval.

Components

Reference ID IdP Adapter
  • Allows PingFederate to integrate with IdP applications for SSO.
Reference ID SP Adapter
  • Allows PingFederate to integrate with SP applications for SSO.
Agentless IdP Java sample application
  • An example IdP application that you can use to test the IdP adapter.
Agentless SP Java sample application
  • An example SP application that you can use to test the SP adapter.
Note:

The sample applications included in the integration .zip archive are built with Java. For sample applications built with other languages, such as .NET Core, PHP, and Python, or to get the latest version of the Java sample applications, see the Ping Identity GitHub repository.

Intended audience

This document is intended for PingFederate administrators.

If you need help during the setup process, see the following sections of the PingFederate documentation:

System requirements

  • PingFederate 9.0 or later
  • Your application must be web-based and able to do the following:
    • Make REST API calls to PingFederate
    • Store a reference ID, resume path, and other values