Improved

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

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.

New

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

Improved

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

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.

Improved

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

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:

Learn more in Creating and updating virtual hosts.

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.