OAuth 2 Authentication Scheme #6
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
||
| + Request | ||
| + Headers | ||
| + Authorization (Token) |
There was a problem hiding this comment.
This unfortunately isn't correct but I'm unsure how to clearly express this. I'm wondering if anyone else has any elegant solutions.
Basically, the Bearer token will be in the Authorization header. It won't be in the header alone which is why this won't work. It will have a suffix like Authorization: Bearer f136803ab9c241079ba0cc1b5d02ee77.
|
I am merging this to be shelved as a draft. The discussion to continue before going to the "accepted" stage. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request extends on the authentication framework (proposed in #4) to provide a base authentication scheme called "OAuth 2".
Dependencies: