-
Notifications
You must be signed in to change notification settings - Fork 63
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
fix: validate JWT token on alias look ahead #114
Conversation
- in order to ensure proper MFA for alias lookahead
bfe33c2
to
ad78abe
Compare
scripts/update_deps.sh
Outdated
@@ -1,37 +0,0 @@ | |||
#!/bin/sh |
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 wonder if the script changes should be a separate PR to make the backport/cherry-picking process easier.
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.
Good point :)
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.
Fixed. Moved to #115
ad78abe
to
16aa741
Compare
- in order to ensure proper validation for alias look ahead the provided JWT token must match the role's configuration.
This PR adds support for validating that a request's JWT token contains the required claims for the bound role.
Design of Change
Validate the JWT token against a known Vault role. If it is deemed to be invalid return an error.
Note: the token is not passed to Kubernetes token review API, as this is only needed for login.