Skip to content
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

The /api/v1/authorized endpoint should accept the token post via HTTP header #160

Closed
tisnik opened this issue Sep 7, 2017 · 0 comments
Closed
Assignees

Comments

@tisnik
Copy link
Member

tisnik commented Sep 7, 2017

Swagger UI says, that the following call should return HTTP code 200 when called with the correct auth.token:

curl -X GET --header 'auth-token: $TOKEN' --header 'Accept: application/json' 'http://$SERVER/api/v1/authorized'

But ATM it works only when the auth.token is stored in the session, ie. the auth-token header is ignored.

It would be nice to be able to send the token via headers as well. TY in advance.

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

2 participants