Skip to content

400 Response when Access Token in Header #51

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

Open
Creeves opened this issue Feb 7, 2017 · 0 comments
Open

400 Response when Access Token in Header #51

Creeves opened this issue Feb 7, 2017 · 0 comments

Comments

@Creeves
Copy link

Creeves commented Feb 7, 2017

I'm able to successfully retrieve an access token using this plugin but when I wish to attach it to an API requests (say /oauth/me/) it only appears to work when the access token is a parameter, rather than a header.

If I hit http://54.253.241.207/oauth/me/?access_token=XXXXXXXXXX the requests returns successfully. Yet when I use the 'Authorization: Bearer XXXXXX' header I get a 400 response with the response {error: "invalid_request", error_description: "Missing or invalid parameter(s)"}.

Am I right to think that authentication using the 'Authorization' header should still work in the free version of the plugin?

Full Gist of the cURL response is here and the header definitely seems to be present.

Thanks for any help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant