WebServer: add support of Authorization: Bearer in HTTP header #22
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 patch implement some parts of RFC 6750 OAuth 2.0 Bearer Token Usage.
Authorization of resource access through the use of a token is limited to
token presence in header fields of HTTP request.
Even if expiration date is not mandatory within tokens, i think most of the time
tokens embeds such data to grant access to resources for a discrete period.
That's why this patch focus on searching for an expiration date within the token,
and store it in a map in case of successful token verification, to speed up next
requests processing with same token.
Since content of tokens is not standardized, callbacks must be provided to keep
the token decode and checks outside of libnavajo.
Signed-off-by: Julien Courtat julien.courtat@aqsacom.com