Hi Stefan,
"If you are this far then I assume other Hawk GET requests work ok? "
Manoj : - Yes, I have made GET /v1/account/keys and receiving the request bundle properly after successful login.
"Do you have any other POST requests that work correctly? Is it just /v1/certificate/sign that is giving you trouble?"
Manoj : - No I am not able to proceed to other post request ( with payload hash ), as they depend on the certificate that we get from /certificate/sign.
"Did you run your unit tests against the example requests from https://github.com/hueniverse/hawk ?"
Manoj : - I am completely unaware of sample request for /certificate/sign.
I saw the code in, /test/client.js and /example/usage.js
should I run a local node.js server to test ?
- If I want to test with my credentials how should I do?
Could you please guide me on how to test post request with payload for /certificate/sign.
Thanks in advance.
> When I'm making a post request to
> /v1/certificate/sign
> I am getting, the following error
> {"code":401,"errno":109,"error":"Unauthorized","message":"Payload is
> invalid","info":"https://github.com/mozilla/fxa-auth-server/blob/master/docs/api.md#response-format"}
The 109 error is "invalid request signature", which means that the Hawk authentication goes wrong.
Your problem can be in two places: the content hash or the request signature.
It looks like your code is correct for the content hash is correct.
Did you run your unit tests against the example requests from https://github.com/hueniverse/hawk ?
If you are this far then I assume other Hawk GET requests work ok? Do you have any other POST requests that work correctly? Is it just /v1/certificate/sign that is giving you trouble?
S.
Thanks,
Manoj
|
|
_______________________________________________ Dev-fxacct mailing list [email protected] https://mail.mozilla.org/listinfo/dev-fxacct
