-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Access token forwarding through nginx auth request #68
Conversation
Related to oauth2-proxy#420. (cherry picked from commit b138872) Signed-off-by: David Holsgrove <david.holsgrove@biarri.com>
(cherry picked from commit 6fab314) Signed-off-by: David Holsgrove <david.holsgrove@biarri.com>
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've seen the original PR before, it inspired the -set-authorization
stuff I worked on! One minor nit and then LGTM
Example should set header as `X-Access-Token` Co-Authored-By: davidholsgrove <davidholsgrove@users.noreply.github.com>
@JoelSpeed yeah no worries - I kept @patrickfuller's commits unmodified, but happy for the readme example to be updated 👍 |
Looking good, please add a note to the Changelog and then we can get this merged |
Done - thanks :) |
Anything else you need from me @JoelSpeed? |
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.
Apologies for not getting back to you on this! One minor thing to do with the change note not being in the right section then we can go
As for the release, probably 2-3 weeks time, there's a few things nearly ready to merge and something I've got planned to get done by around mid march that would be good to get released asap
* Access token forwarding through nginx auth request Related to oauth2-proxy#420. (cherry picked from commit b138872) Signed-off-by: David Holsgrove <david.holsgrove@biarri.com> * Improved documentation for auth request token (cherry picked from commit 6fab314) Signed-off-by: David Holsgrove <david.holsgrove@biarri.com> * Update README.md Example should set header as `X-Access-Token` Co-Authored-By: davidholsgrove <davidholsgrove@users.noreply.github.com> * Update Changelog to reference oauth2-proxy#68 * Fix Changelog message location
Document feature implemented in oauth2-proxy#68 The feature is already decribed in in the nginx example but not clearly on each respective parameters documentation.
* Document set_xauthrequest with pass_access_token Document feature implemented in #68 The feature is already decribed in in the nginx example but not clearly on each respective parameters documentation. * Update docs/configuration/configuration.md Co-authored-by: Nick Meves <nick.meves@greenhouse.io> Co-authored-by: Nick Meves <nick.meves@greenhouse.io>
…auth2-proxy#68) * Feature: Add support for defining custom container securityContext * Bump chart version to 5.2.0
Description
This enables expected behavior when using:
If both of these are set, the access token will be included in an
X-Auth-Request-Access-Token
header, following theX-Auth-Request-*
pattern used forUser
andEmail
.The access token allows for further validation by upstream services.
Motivation and Context
Re-targeting of @patrickfuller's PR from original bitly/oauth2_proxy which wasn't merged before fork to pusher/oauth2_proxy.
Original review and discussion available on the PR and issue:
bitly/oauth2_proxy#424
bitly/oauth2_proxy#420
How Has This Been Tested?
Kubernetes helm charts for oauth2_proxy and keycloak
nginx-ingress annotations;
Confirmed X-Auth-Request-Access-Token received by backend, and successfully decoded the JWT access token.
Checklist: