We have added the HMACSHA256 algorithm to the Netvisor API in production and training environments. Currently, our API supports HMACSHA256, MD5, and SHA256 hashing algorithms for authentication. To enhance security, we plan to phase out outdated and weaker algorithms, such as MD5 and SHA256, and replace them with the HMACSHA256 algorithm.
We request our partners to ensure that your integration implementation supports the new HMACSHA256 algorithm. If support is lacking, we recommend starting development work as soon as possible. We offer assistance and support for implementing the changes if necessary. [email protected]
When testing the new HMACSHA256 algorithm, ensure that the API authentication complies with the documentation guidelines, including these changes. All API partners must adopt the new encryption algorithm during the six-month transition period. We will provide more detailed schedules and instructions separately.
You can make the necessary changes to the integration operation according to this guideline:
Summary of changes:
Add a new HTTP header: TimestampUnix
Add a new HTTP header: UseHTTPResponseStatusCodes
Change the value of the HTTP header MACHashCalculationAlgorithm to HMACSHA256
Update the MAC calculation to use the HMACSHA256 encryption algorithm
___________________
Adding support for HMACSHA256
We have added the HMACSHA256 algorithm to the API in production and training environments. Currently, our API supports HMACSHA256, MD5, and SHA256 hashing algorithms for authentication. To enhance security, we plan to phase out outdated and weaker algorithms, such as MD5 and SHA256, and replace them with the HMACSHA256 algorithm.
We request our partners to ensure that your integration implementation supports the new HMACSHA256 algorithm. If support is lacking, we recommend starting development work as soon as possible. We offer assistance and support for implementing the changes if necessary. [email protected]
When testing the new HMACSHA256 algorithm, ensure that the API authentication complies with the documentation guidelines, including these changes. All API partners must adopt the new encryption algorithm during the six-month transition period. We will provide more detailed schedules and instructions separately.
You can make the necessary changes to the integration operation according to this guideline:
Changes summary:
Add a new HTTP header: TimestampUnix
Add a new HTTP header: UseHTTPResponseStatusCodes
Change the value of the HTTP header MACHashCalculationAlgorithm to HMACSHA256
Update the MAC calculation to use the HMACSHA256 encryption algorithm
This article has been translated using an AI-based translation tool. The contents or wording of these instructions may differ from those in other instructions or in the software.