In July 2021, support ended for HMAC-SHA1 for Token Based Authentication (TBA) integrations in all non-production accounts, such as sandbox, test drives, development, and Release Preview accounts.
Oracle NetSuite will end support for the HMAC-SHA1 algorithm in production accounts for TBA integrations in NetSuite 2023.1. We encourage you to update all your TBA integrations to use HMAC-SHA256 as soon as possible.
What is Changing?
Oracle NetSuite will end support for the HMAC-SHA1 algorithm in production accounts for TBA integrations in NetSuite 2023.1. All your integrations that are still using HMAC-SHA1 will stop working once your account is upgraded to NetSuite 2023.1.
Required Actions
TBA Integrations That May Still Be Using HMAC-SHA1
You must update all your TBA integrations that are still using HMAC-SHA1:
- SOAP web services: You must update the signature algorithm parameter used in the tokenPassport SOAP request. For more information, see TokenPassportSignature, a sub-section of the topic in TokenPassport Complex Type, SuiteAnswers ID 44711.
- RESTlets: You must update the RESTlet authorization header to use HMAC-SHA256. The value of the oauth_signature_method parameter must be changed to HMAC-SHA256, and the value of the oauth_signature parameter also must change accordingly. See Example OAuth Header, SuiteAnswers ID 50996.
For more information, see The Signature for Web Services and RESTlets, SuiteAnswers ID 77576.
Other Applications That May Require Updates
These applications require significant updates to support HMAC-SHA256. If you use the CSV Integrator SuiteApp, or the HTTP Client connector from Boomi, verify that you have updated them as described below.
Note: You may also need to update the Java Runtime Environment (JRE) to a newer version that supports HMAC-SHA256. See the Troubleshooting section of SuiteAnswers ID 101932 for more information.
- HTTP Client Connector from Boomi: In the past, Boomi’s HTTP Client connector used HMAC-SHA1. Customers using Boomi’s HTTP Client connector to connect to NetSuite with OAuth 1.0 could not specify a different signature method. Per instructions from Boomi, as of September 2021 (with September AtomSphere release) you should update your integrations by selecting HMAC-SHA256 in the Signature Method field and redeploy the process.
Creating Your Own Test Window for HMAC-SHA1 for TBA Integrations
To help you prepare for the end of support for HMAC-SHA1, you can temporarily disable HMAC-SHA1 for TBA in your production account. Disabling HMAC-SHA1 helps you discover whether your TBA integrations are still using HMAC-SHA1. See Create Your Own Test Window for HMAC-SHA1 in TBA Integrations, SuiteAnswers ID 100728.
Note: HMAC-SHA1 is not supported in non-production accounts. You can test your integrations for HMAC-SHA1 use if you have access to a sandbox, test drive, development, or Release Preview account.
If you have more questions, please contact NetSuite Customer Support.