PingFederate uses identity provider (IdP) adapters to look up session information and authenticate users in integrated applications.
The integration of local applications with PingFederate is the essential "first-mile" configuration that allows end-users to access protected resources across domains. This process is facilitated through the use of application-integration kits and a robust SDK (see Bundled adapters and authenticators).
PingFederate uses IdP adapters such as the HTML Form Adapter to authenticate users at your site through applications or access-management systems. Go to to configure instances of IdP adapters.
For authentication sources and selectors that are capable of delegating end-user interactions to external web applications, you can create authentication applications to represent them.
You can also set a default URL to which users can be directed during single logout (SLO), and you can look up system endpoints that application developers at your site need to access PingFederate's single sign-on (SSO) and SLO services.
If your PingFederate configuration enables the WS-Trust security token service (STS), the selections under Integration also include menu items for configuring plugin Token Processors and optionally STS Request Parameters, see IdP configuration for STS.