Added custom auth token header support #354
Merged
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.
I have a use-case with an application where I need to send an authentication token via a different header instead of using the Authorization header due to the app (being a proxy type application) needing to pass the Authorization header in a different capacity.
This pull request adds the capability to Sanctum to specify a different method of getting the token from the request by setting a callback to the Sanctum object, falling back to using the bearer token if nothing has been set.