As an application owner, you focus on creating applications. You do not often have time to learn how to integrate single sign-on and access management to protect your applications, and would prefer that your administrator handle it for you.

You also need to test your application with authentication and authorization policies in a variety of different environments before deploying it to your users. Promoting, testing, and tweaking can be time-consuming, especially if you have to rely on others to promote your applications for you.

PingCentral:

  • Makes it possible for you to apply security configurations to your applications yourself, without assistance from an administrator
  • Allows you to promote these applications yourself, when you are ready, rather than submitting a request and waiting for someone else to promote them for you
  • Provides a central monitoring location for greater visibility into applications across deployment life cycles
  • Minimizes the risk of promoting applications with vulnerable security policies within your organization

Extensive training is not required to use PingCentral. However, for the best possible experience, become familiar with how the platform works before getting started.

How PingCentral works

  1. IAM Administrators create standardized OAuth, OpenID Connect, and SAML service provider security configuration templates based on clients and connections they think are worth replicating. Administrators can also assign existing PingFederate and PingAccess applications directly to you, which will display in a list on your Applications page.
  2. You manage the applications assigned to you, and use SAML, OAuth, or OIDC templates to add new applications to PingCentral.
  3. When you’re ready, you can promote applications to the appropriate development environments to test them, and promote them directly to production environments, if your permissions allow.

This diagram shows the tasks application owners can perform using PingCentral.