Final Reminder: End of Support for RSA PKCSv1.5 Scheme for OAuth 2.0

This notice is intended for customers who are still using the RSA PKCSv1.5 scheme in your algorithm for token signing for the OAuth 2.0 client credentials flow. It is still possible to use this scheme until March 1, 2025, but you should update your integrations as soon as possible to make sure they keep working after this day.

What is Changing?

For security reasons, the support is ending for the RSA PKCSv1.5 scheme in algorithms for token signing for the OAuth 2.0 client credentials flow. As of March 1, 2025, integrations using the RSA PKCSv1.5 scheme will no longer work.

Required Actions

Before March 1, 2025, you must update your integrations to use the RSA-PSS scheme. The length of the RSA key must be 3072 bits, or 4096 bits. Alternatively, you can use an EC key instead. The length of the EC key must be 256 bits, 384 bits, or 521 bits. If you use any integrations provided by a third party, you must inform the third party to update the integrations to use the RSSA-PSS scheme, or the EC key. Any integration still using the RSA PKCSv1.5 scheme will stop working after