-
Notifications
You must be signed in to change notification settings - Fork 1.2k
/signin does not pass through any redirect URL #400
Comments
Works for me. How much did your initial attempt differ from
(notice |
Hi, |
For me |
Still doesn't seem to work.
|
Currently,
So if you want to set |
I had the same problem with a redirection from https://auth.example.com to https://app.example.com and I spent whole day solving it. The problem was in following lines of code: Lines 565 to 567 in a94b0a8
When oauth2_proxy receives callback it checks the redirect URL to be relative own domain. Seems to be it done for security reasons. But anyway there are at least two PRs(#461, #464) that created to solve this problem and none of them not merged yet. For now, the only solution is to apply one of the PRs by hand to HEAD and build a binary. P.S. |
You my friend @alikhil are a legend, thanks |
I am using
oauth2_proxy
with nginx +auth_request
. But, virtually always, the callback success drops me on/
rather than on the actual place I was originally going.It doesn't seem like the
X-Auth-Request-Url
header is being handled correctly possibly, or at least the handoff between thesign_in
andstart
doesn't seem to work.The only way I've gotten this to work is by making the 401 redirect to
https://auth.mydomain.tld/oauth2/start?rd=https://whatever.mydomain.tld/realpath
(note that it saysstart
instead ofsign_in
.)The text was updated successfully, but these errors were encountered: