-
Notifications
You must be signed in to change notification settings - Fork 280
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: ignore other auth prefixes #4718
Merged
Geal
merged 15 commits into
apollographql:dev
from
lleadbet:feat/ignore-other-auth-prefixes
Apr 23, 2024
Merged
Changes from 7 commits
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
979052d
first pass at ignoring other auth prefixes using option
lleadbet 221e522
Merge branch 'dev' into feat/ignore-other-auth-prefixes
lleadbet 91ad740
formatting
lleadbet b5d5650
fixing clippy
lleadbet 7ff8fdf
Apply suggestions from code review
lleadbet af4f063
fixing mistaken test changes + pr feedback
lleadbet b6dcdba
Merge branch 'dev' into feat/ignore-other-auth-prefixes
Geal c0dde97
lint
Geal 0343f11
Merge branch 'dev' into feat/ignore-other-auth-prefixes
lleadbet 2baaf20
cargo fmt
lleadbet e4fd8bb
Merge branch 'dev' into feat/ignore-other-auth-prefixes
lleadbet d8d7923
Merge branch 'dev' into feat/ignore-other-auth-prefixes
lleadbet 1d7befd
Merge branch 'dev' into feat/ignore-other-auth-prefixes
lleadbet 5f0cb92
Merge branch 'dev' into feat/ignore-other-auth-prefixes
Geal ad308be
Merge branch 'dev' into feat/ignore-other-auth-prefixes
bnjjj File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
### Ability to ignore other auth prefixes in the JWT plugin | ||
|
||
You can now choose whether to ignore other header prefixes with the JWT plugin. Many applications will use the format of `Authorization: <scheme> <token>` and this will enable the use of other schemes within the `Authorization` header. | ||
|
||
If the header prefix is an empty string, this option will be ignored. | ||
|
||
You can configure this, such as: | ||
|
||
```yaml title="router.yaml" | ||
authentication: | ||
router: | ||
jwt: | ||
header_name: authorization | ||
header_value_prefix: "Bearer" | ||
ignore_mismatched_prefix: true | ||
``` | ||
|
||
In the above, the router will ignore `Authorization: Basic <token>`, but process requests with `Authorization: Bearer <token>` defined. | ||
|
||
By [@lleadbet](https://github.com/lleadbet) in https://github.com/apollographql/router/pull/4718 |
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure we actually need an option. The router looks for the value with the prefix it needs, it ignores the rest, we still have the same behavior as before: if it does not find the value it wants, then the request will not be authenticated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is that right? I thought we returned an
InvalidPrefix
message if we didn't recognise a prefix and that's what Lucas is changing. i.e.: what was an Invalid prefix fail will become, with this option enabled, continue.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the important part is whether
require_authentication
is enabled