Keep getting Cookie is invalid about oauth2_proxy HOT 6 CLOSED

Can you share the command line you are using and a snippet from the logs?

from oauth2_proxy.

2014/12/23 11:50:31 127.0.0.1:55555 ("192.168.28.2") GET /oauth2/start?rd=%2F
2014/12/23 11:50:45 127.0.0.1:55614 ("192.168.28.2") GET /oauth2/callback?state=/&code=*****************************************
2014/12/23 11:50:45 validating: is ore@****.com valid? true
2014/12/23 11:50:45 127.0.0.1:55614 ("192.168.28.2") authenticating ore@*******.com completed
2014/12/23 11:50:45 127.0.0.1:55616 ("192.168.28.2") GET /
2014/12/23 11:50:45 127.0.0.1:55616 ("192.168.28.2") - invalid cookie session

I am using a config file you can take a look at the base config I am using

vic3lord/google-auth-proxy

from oauth2_proxy.

hmm. might this be because there isn't a cookie secret set?

from oauth2_proxy.

There is actually

Sent from my iPhone

On Dec 23, 2014, at 16:21, Jehiah Czebotar [email protected] wrote:

hmm. might this be because there isn't a cookie secret set?

—
Reply to this email directly or view it on GitHub.

from oauth2_proxy.

ok, i was going based on here but i'm not intimately familiar with Chef cookbooks.

This sounds like a round-trip problem with cookies where they are getting set and either not passed back to the browser, or set in a way the browser isn't passing them back.

Can you verify that the browser get's a Set-Cookie header on the response from /oauth2/callback?state=/&code=... and that the same value is passed to the next request to /? It should be straight forward to inspect that using the chrome/firefox developer tools.

Presumably you are proxying though a ssl term endpoint, do you have any thoughts about configuration there that might get in the way? If you are not terminating through a SSL endpoint (i've considered adding https support directly to google_auth_proxy to make that setup easier) you might be encountering an issue with cookie_https_only being set to true so the browser is not passing the cookie back over a http connection.

from oauth2_proxy.

Found the problem you were right...
By default if you use config file (at least from what I checked) cookie_https_only is set to true

I just set it to false

from oauth2_proxy.