PingAccess allows you to protect sites, APIs, and other resources using rules and other authentication criteria. Working in conjunction with a configured token provider, PingAccess integrates identity-based access management policies through a federated corporate identity store using open standards access protocols.

Note:

Valid token providers include PingFederate and other common token providers with the OAuthOAuth A standard framework that enables an application (OAuth client) to obtain access tokens from an OAuth authorization server for the purpose of retrieving protected resources on a resource server. 2.0 and OpenID Connect (OIDC)OpenID Connect (OIDC)OIDC An authentication protocol built on top of OAuth that authenticates users and enables clients (relying parties) of all types to request and receive information about authenticated sessions and users. OIDC is extensible, allowing clients to use optional features such as encryption of identity data, discovery of OpenID Providers (OAuth authorization servers), and session management. protocols. For more information, see System requirements.

To help you get the most from PingAccess, this document offers insights about the product, such as:

As you learn about PingAccess's features and functions, review Configuring and Customizing PingAccess for instructions on how to configure them.

For a comprehensive set of instructions on using the PingAccess interface, see the PingAccess User Interface Reference Guide.