--whitelist-domain doesn't respect protocol on redirect about oauth2-proxy HOT 4 CLOSED

http vs https is selected for automatic redirect-url based on the cookie-secure option, so if you enable cookie-secure you should get https
https://github.com/pusher/oauth2_proxy/blob/v3.1.0/oauthproxy.go#L256-L257

from oauth2-proxy.

Enabling the flag --cookie-secure worked, but it requires users to have 3th-party cookies enabled in the browser, otherwise they get an error. There is no way to enable HTTPS on the redirect url without having to set cookie-secure set to true?

from oauth2-proxy.

Enabling the flag --cookie-secure worked, but it requires users to have 3th-party cookies enabled

I find this to be a surprising requirement.

There is no way to enable HTTPS on the redirect url without having to set cookie-secure set to true?

Besides a single hard-coded redirect url, no, sorry ... fastest way at this point would be to edit the code and re-build. Or maybe some nginx rules could rewrite the location header.

from oauth2-proxy.

I may have jumped into conclusions too quickly. There was something on my firefox installation causing problems, but seems like it's not related to 3th party cookies, i couldn't reproduce the problem with chrome and 3th party cookies disabled.

After clearing cache and cookies in firefox it started to work just fine. Thanks for the help @ploxiln ! i'm closing the issue.

from oauth2-proxy.