Deprecation of HMAC-SHA1 for Token-based
Authentication (TBA)
As of 2021.1, it is no longer possible to create new solutions for use with the HMAC-SHA1 signature
method for Token-based Authentication (TBA). You can still use the HMAC-SHA256 signature method to
create new solutions for use with TBA.
As of 2021.2, any solutions using the TBA feature with HMAC-SHA1 as a signature method will stop
working. You must update your TBA integrations to use HMAC-SHA256 before your account is upgraded
to 2021.2. This limitation also applies to any third-party integration.
Before 2021.2, you must update your authorization header to use HMAC-SHA256. To do so, change
the value of the oauth_signature_method parameter to HMAC-SHA256. The value of the oauth_signature
parameter should change accordingly. For more information, see the help topic Example OAuth Header.
Important: If you are using a library for signing, verify whether the library supports HMACSHA256, and if needed, update the library with HMAC-SHA256 support.