Skip to content

Authorization Header format clarification #15

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.

Sign up for GitHub

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

Jump to bottom
Open
brianv0 opened this issue Apr 9, 2018 · 2 comments
Open

Authorization Header format clarification #15

brianv0 opened this issue Apr 9, 2018 · 2 comments

Comments

@brianv0
Copy link

brianv0 commented Apr 9, 2018

It seems like the default Authorization header format for an HTTP request is of the form:

Authorization: Bearer realm="scitokens.org" ${token}

Is this codified somewhere? Is it safe to assume?
@jbasney
Copy link
Member

jbasney commented Apr 9, 2018

Good question. https://tools.ietf.org/html/rfc6750#section-2.1 says the request should be "Bearer" 1*SP b64token and I think realm only belongs in the response, not the request.

@brianv0
Copy link
Author

brianv0 commented Apr 9, 2018

Good enough for me, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jbasney @brianv0