New features

Ticket ID Description
PASS-939 In addition to seeing the list of applications managed within PingCentral, administrators can see all of the applications that exist in connected PingFederate environments. This enhanced view makes it easy for administrators to review application configurations, and quickly save the configurations as templates or add them directly to PingCentral without going through the Add Application wizard.
PASS-1115 Administrators can filter their application lists by environment, template, application owner, integration type (OAuth and OIDC or SAML), management type (managed or unmanaged), or by using any combination of these filters.
PASS-1318 Administrators can restrict application owners from promoting their applications to specific environments. Protected environments display shield icons next to their names within PingCentral.
PASS-1469 Administrators and application owners can change the templates associated with SAML applications, rather than creating new applications using different SAML templates. Attribute mappings will likely need to be recreated before the application is promoted.
PASS-1525 Administrators can run PingCentral as a Linux systemv service, a Linux systemd service, or a Windows service.
PASS-1826 Administrators can configure PingCentral to use the MySQL relational database management system instead of using the default H2 database.
PASS-1832 The ACS URL is used to promote SAML applications instead of the base URL.
PASS-2016 Certificates are no longer required to promote SAML applications that do not require SP certificates.
PASS-2158 Administrators and application owners can sort their application lists by modified date or application name.
PASS-2203 After application owners promote their SAML applications, the SSO endpoint URL displays on the Promotion Details window and is available for them to give to their service providers.


Administrators can use the Linux or Windows upgrade utility to upgrade from PingCentral version 1.0.1 to version 1.2.0. PingCentral cannot be upgraded directly from version 1.0.0 to 1.2.0.
PASS-2925 When adding environments, users who select the Skip Verification option and enter passwords with more than 32 characters receive data integrity violation errors.

Resolved issues

Ticket ID Description
PASS-2496 Administrators can now update logging files directly through the log4j2.xml file instead of accessing the file.

Known issues

Ticket ID Description
PASS-1552 When updating a user's role, the Discard Changes button does not currently work.
PASS-1998 When an OAuth/OIDC application is promoted from PingCentral to PingFederate, the secret is captured and saved. If this application is removed from PingCentral and a new application is created with the same name, promotions to PingFederate will use the client secret provided for the original application instead of the new secret that was provided in the new application. There is currently no way to retrieve the secret that was provided for the original promotion.
PASS-2090 If SSO is configured for PingCentral and PingFederate is unavailable, PingCentral will fail to start. If this occurs, determine why PingFederate is unavailable, resolve the issue, and restart PingCentral.
PASS-2093 When SSO is enabled, custom session settings are modifiable, but are not honored.
PASS-2097 When SSO is enabled, an administrator is able to update and add users to PingCentral through the User Management page, even though it has no effect.
PASS-2119 Protected environment text on the Environments page refers to “production,” even if the protected environment is not a production environment.
PASS-2122 When modifying an environment, if an identity provider certificate is added or updated, and then the PingFederate admin password is updated, the cursor will jump down to the IDP Certificate Password field each time a key is pressed.
PASS-2468 Administrators cannot update user information if PingCentral does not contain any environments.
PASS-2526 If PostgreSQL is set up without a database, PingCentral will fail to start. To prevent this from happening, add the database to the server prior to starting PingCentral.
PASS-2528 Users who attempt to create a SAML application without a signing key pair might receive a server error.
PASS-2740 Unverified environments should not display when templates and applications are added to PingCentral, and when applications are promoted. If selected, users receive an error message.
PASS-2766 Using special characters when searching on the Environments, Templates, and Users pages results in a server error.
PASS-2783 The sorting feature is case sensitive for applications managed within PingCentral.
PASS-2819 If an OAuth application is added from an environment that does not use a client secret to authenticate, the Client Secret field displays, but is ignored. This display could cause confusion, as users can add and generate client secrets for their applications, but the secrets are not saved as expected.
PASS-2824 Users who enter invalid application names when updating their SAML applications do not receive an error message.
PASS-2872 Administrators who are deleted or demoted to an Application Owner role can still perform administrative tasks during an open session.
PASS-2879 When updating SAML applications, PingCentral does not indicate whether certificates are optional.
PASS-2888 After an environment is created in PingCentral, the administrator must refresh the page before they can add a user.
PASS-2925 When adding environments, users who select the Skip Verification option and enter passwords with more than 32 characters receive data integrity violation errors.