---
title: "Ping"
slug: "ping"
updated: 2025-03-03T11:36:40Z
published: 2025-03-03T11:36:40Z
canonical: "docs.plainid.io/ping"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.plainid.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Ping

_PlainID offers an IDP Authorizer integration pattern for this third-party vendor. For more information, see_ [_IDP Authorizers_](https://docs.plainid.io/docs/idp-authorizers){target=`_blank`}.
  
The integration between PlainID and Ping Identity enables organizations to apply a continuous Authentication-Authorization process. The PlainID Ping Authorizer will continue the Authentication process carried out by Ping Federate, to provide the full adaptive access the user is entitled to.

The main objective of Ping, as an IdP (Identity provider), is to handle the authentication process, this is mostly done based on well-defined protocols such as OIDC and SAML. The outcome of the process is an authentication token. During the Authentication process, the PlainID Ping Authorizer dynamically calculates and provides a list of claims based on the policies defined within PlainID. These claims will be used to enrich the token generated by Ping for the authenticated user. The objective of the token enrichment flow is to dynamically and contextually calculate and provide the list of claims (Authorizations) to Ping, as part of the login process.

Refer to the [Ping Configuration](/v1/docs/ping-configuration){target=`_blank`} article to learn how to set it up with your IDP Token Enrichment Service.

![Copy of MarketectureDiagram \(4\).pptx \(3\).png](https://cdn.document360.io/726c7002-05a9-480e-b986-42c9e8824acd/Images/Documentation/Copy%20of%20MarketectureDiagram%20%284%29.pptx%20%283%29.png){height="" width=""}