I have been using this API for a while now, and I've sailing along smoothly... today I started getting "401: Unauthorized" errors after the OAuth process (through my Rails App error logs). I then tried using the ”Netflix Authentication walkthrough" page and got an "Invalid Signature" response when requesting a Access Token in the second to last step (i believe).
Hi, Henry. I've just peeked at your app name and credentials through our administrative page, filled them in on the Walk-Through, and gotten myself signed in to Pikkn. It shows on my Third Party Access page, here:
http://www.netflix.com/ThirdPartyAccess
... so I think everything is working on our end.
Please check that you are sending us the correct API key, shared secret, and application name?
Can you try using the OAuth Test Page <http://developer.netflix.com/resources/OAuthTest> to see if the signature value generated there matches up with what your code is generating?
(If you click on the light gray "Advanced" at the bottom right of the form, you'll get extra fields you can set as well as a display of the OAuth SBS string used to generate the signature.)
Hello,
I have been using this API for a while now, and I've sailing along smoothly... today I started getting "401: Unauthorized" errors after the OAuth process (through my Rails App error logs). I then tried using the ”Netflix Authentication walkthrough" page and got an "Invalid Signature" response when requesting a Access Token in the second to last step (i believe).
Anyone have any thoughts?
Thanks very much!!!
Henry
___
http://pikkn.com
Message edited by Thinking Ahead LLC 3 years ago
Tags
Kent Brewster – 3 years ago
Hi, Henry. I've just peeked at your app name and credentials through our administrative page, filled them in on the Walk-Through, and gotten myself signed in to Pikkn. It shows on my Third Party Access page, here:
http://www.netflix.com/ThirdPartyAccess
... so I think everything is working on our end.
Please check that you are sending us the correct API key, shared secret, and application name?
--Kent
JR Conlin – 3 years ago
Bad signatures are usually a pain to debug.
Can you try using the OAuth Test Page <http://developer.netflix.com/resources/OAuthTest> to see if the signature value generated there matches up with what your code is generating?
(If you click on the light gray "Advanced" at the bottom right of the form, you'll get extra fields you can set as well as a display of the OAuth SBS string used to generate the signature.)