This notice applies to customers who are 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 to be ready for the October 16, 2024, test window.
What is Changing?
For security reasons, the support is ending for the RSA PKCSv1.5 scheme in algorithms used for token signing in the OAuth 2.0 client credentials flow. As of March 1, 2025, integrations using the RSA PKCSv1.5 scheme will no longer work.
What Will Happen During this Test Window?
The planned 24-hour test window will help you identify any OAuth 2.0 integrations in your NetSuite account that are still using the RSA PKCSv1.5 scheme in your algorithm for token signing for the OAuth 2.0 client credentials flow. During the test window, the RSA PKCSv1.5 scheme will not be allowed and the integrations using it will not work.
The 24-hour test window will begin on Wednesday, October 16, at 09:00 a.m. Central Time (CT).
After the test window ends, OAuth 2.0 integrations in your NetSuite account that are using the RSA PKCSv1.5 scheme will start working again, until the end of support.
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 March 1, 2025.
For more information and examples, see OAuth 2.0 Client Credentials Setup, SuiteAnswers ID 101101.
The 24-hour test window in your account will begin on Wednesday, October 16, 2024, at 09:00 a.m. CT.
If you have more questions, please contact NetSuite Customer Support.