Fix expired token message in Exception header #37196
Closed
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
We're adding a WWW-Authenticate header to indicate the token is expired. This commit fixes the error message we return as part of this.
jkakavas
added
>bug
v7.0.0
:Security/Authentication
|
Pinging @elastic/es-security |
jaymode
requested changes
Jan 7, 2019
There was a problem hiding this comment.
I don't think this is right. See https://tools.ietf.org/html/rfc6750#section-3.1. invalid_token is the proper response for an expired token
|
True ! Thanks for keeping me honest here, I failed to check the spec. |
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.
We're adding a WWW-Authenticate header to indicate the token is
expired. This commit fixes the error message we return as part of
this.
Resolves elastic/kibana#27919