Deprecation notices

Ping Identity is no longer provisioning the IDC.CLI OAuth 2.0 client in new tenants and has deprecated it in existing tenants.

If you have any automation or scripts that rely on using the IDC.CLI OAuth 2.0 client in existing tenants, you must update them to use a service account before the end-of-life date when the client will be removed.

Ping Identity has deprecated the use of resource version 1.0 to access ESV REST API endpoints in Advanced Identity Cloud.

In the short term, you can continue to use the 1.0 resource version to access to ESV REST API endpoints, but this won’t be possible after the end-of-life date.

If you have any automation or scripts that rely on using the 1.0 resource version for ESV REST API endpoints, you must update them to use resource version 2.0 before the end-of-life date.

Ping Identity has deprecated use of the fr:idm:* scope to access ESV REST API endpoints in Advanced Identity Cloud.

In the short term, you can continue to use the scope to access ESV REST API endpoints, but this won’t be possible after the end-of-life date.

If you have any automation or scripts that rely on using the scope for ESV REST API endpoints, you must update them to use the fr:idc:esv:* scope or an appropriate child scope (fr:idc:esv:read, fr:idc:esv:update, or fr:idc:esv:restart) before the end-of-life date.

Ping Identity has deprecated Autonomous Access. The product will reach end of life on October 31, 2025. During the deprecation period, Ping Identity will not provide new patches, updates, or new features for Autonomous Access.

To support our Autonomous Access customers, we’re providing migration assistance to PingOne Protect. This advanced threat detection solution leverages machine learning to analyze authentication signals and detect abnormal online behavior. PingOne Protect is a well-established product trusted by hundreds of customers worldwide.

The Autonomous Access documentation has moved to the documentation archive at https://docs.pingidentity.com/archive/.