trim whitespaces from the token before validation check #433
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.
Sometimes users accidentally pass sanctum tokens in the request header with leading or trailing white-spaces (two white-spaces between the word "Bearer" and the token), like in:
Currently, this results in an unexpected
401
with{"message":"Unauthenticated."}
response from the application even though the token is correct. This can confuse the user. In this change tokens from the$request
with leading or trailing white-spaces should be trimmed such that correct token are accepted and not denied.