PingOne Advanced Services

PingOne Advanced Services Release Notes

Review release notes for PingOne Advanced Services.

Subscribe to get automatic updates: PingOne Advanced Services release notes RSS feed

  • PingOne Advanced Services platform version 2.1 is the final version that supports basic authentication for the PingFederate and PingAccess Admin APIs. After platform version 2.4 releases, 2.1 will move into extended support and six months later will reach its End of Life (EOL) status, as outlined in our Support policy. Exceptions to this policy will be granted on a case-by-case basis.

Platform version 2.1.5 (June 2026)

This platform version deploys with these microservices and applications:

Enhancements

PingDirectory restart process improved

Improved

This update introduces a simplified deployment and configuration pattern for PingDirectory.

Platform version 2.1.1 (September 2025)

This platform version deploys with these microservices and applications:

We’ve also updated these microservices and applications, which are available for platform version 2.1.1:

PingFederate 2.1.5 (June 2026)

PingAccess 2.1.5 (June 2026)

PingAccess 2.1.4 (April 2026)

PingAccess 2.1.3 (March 2026)

PingFederate 2.1.4 (March 2026)

PingFederate 2.1.3 (January 2026)

PingFederate 2.1.2 (October 2025)

Enhancements

Use OAuth to access the PingFederate Admin API

New

To connect to the PingFederate API, get an access token. This token can be retrieved using an authorization code flow or a client credentials flow.

If you choose to use a client credentials flow, connections must be correctly configured for self-managing administrator accounts.

For improved security, basic authentication for the PingFederate Admin API has been deprecated and will be removed in PingOne Advanced Services version 2.2.

Platform version 2.1.0 (May 2025)

This platform version deploys with these microservices and applications:

Enhancements

Use OAuth to access the PingAccess Admin API

New

If you choose to use a client credentials flow, connections must be correctly configured for self-managing administrator accounts.

For improved security, basic authentication for the PingAccess Admin API has been deprecated and will be removed in PingOne Advanced Services version 2.2.

LDAPS custom domains now supported

Improved

PingDirectory LDAPS URLs are now routed through NGINX, which has improved system flexibility and supports custom domains.

Automated certificates for global DNS domains now available

Improved

Those using Let’s Encrypt certificates to ensure that communications between PingOne Advanced Services products and services remain encrypted and secure (used by default), can now create automated certificates for global DNS domains.

Logging improvements

Improved

Internal log pipeline stability improvements have been made, which will further help you observe and maintain your system.

Platform version 2.0.1 (April 2025)

This platform version deploys with these microservices and applications:

We’ve also updated these microservices and applications, which are available for platform version 2.0.1:

PingFederate 2.0.2 (November 2025)

PingDirectory 2.0.3 (March 2026)

Platform version 2.0.0 (December 2024)

This platform version deploys with these microservices and applications:

Enhancements

Self-service API Beta now available

New

You and your administrators can now create and update virtual host certificates and TLS configurations yourselves through a self-service API. Configurations are automatically replicated to child regions in PingOne Advanced Services for the following applications:

  • PingFederate

  • PingFederate Admin API

  • PingAccess

  • PingAccess Admin API

  • PingAccess Agents

  • PingDirectory

  • Delegated Admin

If you don’t want to create or update virtual hosts yourself, you can still submit a service request. Select Advanced/Other as your requested capability, provide a detailed description of your needs, and submit your request to the Support team.

You’ll need to configure access to the administrative API before you can add or update virtual hosts. Learn more about configuring the API in Configuring access to the administrative API.

You’ll also need to add the SelfService attribute. Learn more about these attributes in Creating custom user attributes. Then, update the application with the appropriate attribute mappings.