6-hour test window to test HMAC-SHA1.You are receiving this notification because you use the Token-based Authentication (TBA) feature in your account for integrations. These TBA integrations may be using HMAC-SHA1 as a signature method. With the NetSuite 2022.1 release, HMAC-SHA1 will no longer be supported as a signature method for TBA integrations. Before your account is upgraded to 2022.1, you must update your TBA integrations to use the HMAC-SHA256 signature method. Oracle NetSuite has planned a test window for Tuesday, August 17, 2021. The test window will help you identify integrations in your account that still use HMAC-SHA1. The Boomi HTTP Client Connector and HMAC-SHA1 You may be using the Boomi HTTP Client connector. If your connection uses OAuth 1.0, your connections will be affected because the Boomi HTTP Client connector currently only supports HMAC-SHA1. Important: Boomi is currently updating the HTTP Client connector so that you can select the signature method and use HMAC-SHA256. This updated version of the connector is targeted for availability on August 14, 2021. For more information, see the NetSuite HMAC-SHA1 Signature Deprecation Update article posted in the Boomi Community. Note: Boomi’s NetSuite connector will not be affected by the test window because it currently uses HMAC-SHA256. What is Changing? NetSuite TBA is changing to only support HMAC-SHA256. When your account is upgraded to NetSuite 2022.1, any integrations that use TBA with HMAC-SHA1 as a signature method will stop working. This applies to all integrations in your account, including integrations from third-party solution providers. Upgrades to NetSuite 2022.1 are targeted to occur between February and April of 2022. What Will Happen During this Test Window? The upcoming 6-hour test window will help you identify integrations in your NetSuite account that are still using HMAC-SHA1. During the test window, HMAC-SHA1 will not be allowed and any integrations using it will stop working. Test Window Schedule The 6-hour test window begins on Tuesday, 08:00 EDT, August 17, 2021 (5:00 am PDT) and ends at 2:00 PM EDT (11:00 a.m. PDT.) After the test window ends, TBA integrations using the HMAC-SHA1 signature method will be accepted again, until the NetSuite 2022.1 upgrade occurs. Required Actions Update your TBA integrations to use the HMAC-SHA256 signature method. If you use any integrations provided by a third party, you must inform the third party that 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 2022.1 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 also 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. If the library you are using does not support HMAC-SHA256, you must either update the library to use HMAC-SHA256 or start using another library that supports HMAC-SHA256. If you are using the HTTP Client Connector from Boomi, update to the new version when it becomes available on Saturday, August 14, 2021. See NetSuite HMAC-SHA1 Signature Deprecation Update for more information. The 6-hour test window in your account begins on Tuesday, 08:00 EDT, August 17, 2021. If you require assistance or more information, please contact NetSuite Customer Support. Thank you, The Oracle NetSuite Team