-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
oauth2: use issuer-prefixed auth URL in challenge redirect #509
Conversation
Hey thank you for your contribution! Could we maybe add a fallback in case the |
Sure, but what are valid uses of Hydra with an empty issuer (versus, say, the default of |
If you just want to play with it and run it locally, or as part of the tests, such a fallback makes sense. It should be easy to get started with Hydra (it's hard enough already ;) ) so let us make this as easy as possible! |
100% agree; the When
|
HOST is unfortunately often not the real hostname, but rather the interface that hydra is listening on, this is why I used r.RequestURI in the first place here :) |
Right, so, when starting out or testing locally it would work (because |
Host defaults to empty catching all interfaces which is why hydra works per default in a docker container |
🤦♂️ sorry; was reading the documentation wrong. I'll add the fallback. |
In order to support running Hydra with a different path prefix behind a proxy, issue a challenge token with an issuer-prefixed auth redirect URL instead of the URL received with the auth request. Signed-off-by: Wyatt Anderson <[email protected]>
48323d5
to
d2ede4c
Compare
Thank you! |
In order to support running Hydra with a different path prefix behind
a proxy, issue a challenge token with an issuer-prefixed auth redirect
URL instead of the URL received with the auth request.
Based on discussion in #352