• Removes many tasks from your list of responsibilities, which lowers operational costs and reduces bottlenecks.
  • Provides a central monitoring location for greater visibility into applications across deployment life cycles.
  • Minimizes the risk of promoting applications with vulnerable security policies and makes it easier to standardize policies across the applications within your organization.

Using PingCentral does not require extensive training. However, for the best possible experience, review how the platform works before getting started.

How PingCentral works

This flowchart illustrates the tasks that IAM Administrators perform when using PingCentral.
  • In PingCentral, you set up users and define PingFederate and PingAccess development, test, and production environments.
  • In PingFederate and PingAccess, you locate clients, connections, and application security configurations worthy of replicating.
  • In PingCentral, you create PingFederate OAuth, OpenID Connect (OIDC), SAML, and PingAccess application templates based on these clients, connections, and applications by using the template wizard, by saving them as templates, or by adding them directly to PingCentral.
    This flowchart illustrates the tasks IAM Administrators perform when using PingCentral.

This flowchart illusrates the tasks that application owners perform when using PingCentral.

In PingCentral, application owners manage the applications assigned to them and use your templates to apply OAuth, OIDC, SAML SP, and PingAccess security configurations to them. A wizard guides them through the process of providing a name and description for each application they create as well as environment-specific information that makes it possible to run the application on the target environment.
This flowchart illustrates the tasks application owners perform to add applications to PingCentral and promote them to development, staging, or production environments.

To see which PingFederate components are used to authenticate clients and connections in PingCentral, see OIDC connection orchestration and SAML connection orchestration.

For a deeper understanding of how PingAccess applications work, see PingAccess application deployments and configurations.