You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the same values for noone, timestamp and the secret keys, I get the following from another tool (Paw):
GET /route HTTP/1.1
Authorization: OAuth oauth_consumer_key="abc", oauth_nonce="rbox6F", oauth_signature="221yLZJVIBt8WpXZw1kVAsh8K9c%3D", oauth_signature_method="HMAC-SHA1", oauth_timestamp="1482285391", oauth_token="mno", oauth_version="1.0"
Host: abc.xyz
Connection: close
User-Agent: Paw/3.0.14 (Macintosh; OS X/10.12.0) GCDHTTPRequest
Notice how the oauth_signature values differ for the two requests.
The request I made with Paw gets authenticated successfully while the request I made with Supertest(with headers generated by oauth) fails with the message 'signature does not match'.
Can anyone please verify if oauth.authHeader() generates a valid Authorization header?
The text was updated successfully, but these errors were encountered:
I have:
I then generate an authorization header and add it to a node HTTP packge(Supertest) as follows:
This gives me the following HTTP header:
Using the same values for noone, timestamp and the secret keys, I get the following from another tool (Paw):
Notice how the
oauth_signature
values differ for the two requests.The request I made with Paw gets authenticated successfully while the request I made with Supertest(with headers generated by oauth) fails with the message 'signature does not match'.
Can anyone please verify if
oauth.authHeader()
generates a valid Authorization header?The text was updated successfully, but these errors were encountered: