AN_ERROR_OCCURRED_WHILE_DECRYPT_PASSWORDGUID const secretKey = crypto.createSecretKey({ secret: key, encoding: https.Encoding.UTF_8, }); log.debug("secretKey", secretKey); const hmac = crypto.createHmac({ algorithm: crypto.HashAlg.SHA256, key: secretKey, }); log.debug("hmac before", hmac); hmac.update({ input: message, inputEncoding: https.Encoding.UTF_8, }); log.debug("hmac after", hmac); return hmac.digest({ outputEncoding: https.Encoding.BASE_64, });

AI generated answer (using internal Slack threads):

Based on the conversations, it seems that the users are discussing the use of HMACs (Hash-based Message Authentication Codes) in the context of NetSuite's SuiteScript and AWS4 authentication. They are trying to generate HMACs of elements of the secret and request, which become the key for the next HMAC. However, they are facing issues as the N/crypto module in SuiteScript seems to only create HMACs with keys stored in the secrets management. One user suggests using Crypto.JS from Google and provides a function for generating the AWS signature. However, another user asks if there's a way to do this with the native crypto module in SuiteScript. The response indicates that the native crypto module in SuiteScript is not suitable for dynamic keys and expects the cryptographic key to be stored in the secret, not computed. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******