AP-5754 support for providing custom header name for auth prehandler #222
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
kjamrog
requested review from
kibertoad,
CarlosGamero,
drdaemos and
a team
as code owners
kibertoad
approved these changes
Dec 4, 2024
CarlosGamero
approved these changes
Dec 4, 2024
kjamrog
deleted the
AP-5754_support_for_providing_header_name_in_auth_prehandler
branch
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.
Changes
createStaticTokenAuthPreHandleroperated only onauthorizationheader, which is a limitation in case we would like to use different one. This PR allows to provide header name as a parameter, whileauthorizationremains default oneChecklist
major,minor,patchorskip-release