-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with HMAC created using Crypto-JS #1
Comments
Is it an HMAC 512 in the server? I think it might be HMAC 256. Can you check? -DC
|
I should have mentioned: I've used crypto-JS in multiple different clients against this code and it works. -DC
|
We are using SHA512. Below is the code. Can you please post cryptoJS code. We are creating HMAC using crypto-JS and sending the request to Proxy. We have created a Java call out using "hmac-edge-callout.jar" to verify the HMAC. I am new to APIGEE, any suggestions will be helpful. Please find below code.
|
Hi,
We are using Crypto-js to create HMAC and send the request to the Proxy.
The HMAC which is created using JAVA "hmac-edge-callout.jar" is different.
var buffer = new Buffer(hashSign);
var toBase64 = buffer.toString('base64');
The text was updated successfully, but these errors were encountered: