This notice is intended for customers who use the Token-based authentication (TBA) feature in your account for integrations that use HMAC-SHA1 as a signature method. In NetSuite 2021.2, this method will be deprecated. You must change your integrations to use HMAC-SHA256 as the signature method.
What is Changing?
When your account is upgraded to NetSuite 2021.2, any integrations that are using the Token-based Authentication (TBA) feature with HMAC-SHA1 as a signature method will stop working. This applies to all integrations you create, as well as integrations from the third-party solution providers. The NetSuite 2021.2 release upgrade is targeted to occur between August and October of 2021.
Required Action:
Before your account is upgraded to NetSuite 2021.2, ensure that the TBA integrations in your account are using HMAC-SHA256. If you use any integrations provided by a third party, you inform the third party that the HMAC-SHA1 will no longer be supported as a signature method for TBA in NetSuite. The third party must provide you with an updated solution before the NetSuite 2021.2 release.
You must update the authorization header to use HMAC-SHA256. The value of the oauth_signature_method parameter must be changed from HMAC-SHA1 to HMAC-SHA256, and the value of the oauth_signature parameter must change accordingly. For more information, see the help topic Example OAuth Header (SuiteAnswers, ID 50996).
If you are using a library for signing, you must verify whether the library supports HMAC-SHA256, and update the library to use HMAC-SHA256, if needed. If your library does not support HMAC-SHA256, you must start using a library that supports HMAC-SHA256.