I recently got this in an email from NetSuite: “You are receiving this notification because you use the Token-based Authentication (TBA) feature in your account for integrations that use HMAC-SHA1 as a signature method. As of NetSuite 2021.2, the use of HMAC-SHA1 will be deprecated. Before your account is upgraded to 2021.2, you must change your integrations to use HMAC-SHA256 as the signature method.“
It sounded ominous, but turned out not to be a huge effort. If you’re like me, this TBA stuff captured my attention just long enough to get it working. So getting back into it took a little refamiliarizing. Hopefully this will save you some time.
In my post SuiteTalk TBA Example in C#, you’ll find the following code snippet. Here are the changes required to move from HMAC-SHA1 to HMAC-SHA256. I commented out the old block to highlight what changed.
3 thoughts on “SuiteTalk 2021.2 Deprecating HMAC-SHA1”
Hi, tried following your instructions to change from HMAC-SHA1 to HMAC-SHA256, however, I;m encountering “invalidCredentialsFault”. Looking at the Login Audit Trail, error is pertaining to “UnknownAlgorithm” :(((( Please help :(((
I’m only guessing based on the feedback you supplied. The DOT.net framework supplies both algorithms. If you’ve correctly swapped from HMAC-SHA1 to HMAC-SHA256, it should be accepted by the API. Based on the error, it sounds like it is using something other than either of these two algorithms. I realize this is not much help, but it is the best I can do.
Hi Kevin! Thanks for your help! Got it to work already. XD Apparently, I wasn’t able to successfully make the changes to SHA256, that’s why I kept on getting the error. Using HMAC-SHA1 will constantly yield UnknownAlgorithm error in Login Audit Trail 🙂
Thanks so much for your help! 😀