-
Notifications
You must be signed in to change notification settings - Fork 789
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
400: Bad Request - OAuth state missing from cookies (Google auth) #1028
Comments
I am getting 500 Internal server error when autheticating with GITLAB-CE seems like authentication-state cookies expiration issue cleared browser cookies and cache and any saved data and in New Tab opened https://localhost Name:- xsrf Name:- username-localhost-8888
The one which disappeared was Name :- oauthenticator-state -------------------Once landed on gitlab-CE login----------------------------------- Name:- _gitlab_session ---------------------loged in to gitlab with username----------------------------- --------------------Once Clicked on authosise in gitlab------------ Name:- username-localhost-8888 GOT 500 INTERNAL SERVER ERROR If issue is due authentication state cookies expiring before creating then how to solve it |
this is epic fail bug never fix lol |
Hmmm, cookies are valid in various domains. I recently learned about what HTTP=true cookies imply and that should be fine still. It makes the cookie inaccessible from javascript but is still passed when making HTTP requests from the browser/client when GET/POST-ing etc to a webserver. I'm not confident about what goes on, but cookies are things on the browser being passed to the webserver when making requests etc, and depending on the domain, different cookies are sent. So if facebook.com stores a cookie with HTTP=true on the browser by returning a "Set-Cookie" response header, it will be sent back to the webserver when the browser makes the next request back to facebook.com, but only facebook.com So, if you browse what cookies are available while on google.com, those relates to google.com, and google.com will certainly store various auth related cookies, but jupyterhub wants to store a separate one i assume. Hmmm, questions:
Info:
|
Is there someone having a functional google authenticator up and running? |
Not sure if it's related, but while trying to debug this I ran
|
@consideRatio, I now have a functional Google authenticator running. What worked was to use the latest development release of the helm chart ( And, to solve the error I was getting above I added the following to
which I tried because I saw a similar issue here: #1244 |
Yes I do |
Is there plans to get this out in stable release version? |
I dont have a clear idea about when this issue occur or why yet :/ |
I had this same error "400: Bad Request - OAuth state missing from cookies" when using (Google auth) |
had to remove hostedDomain as well also helm chart version 0.8.2. |
I'll go ahead and close this issue for now, please open a new issue if this fails on 0.9.0+. |
Hi,
I want to use Google authentication with JupyterHub. The problem is that cookie "oauthenticator" that get set up by JupyterHub disappears once Google redirects from oauth page back to Jupyter. Thus I see
and on refresh
I noticed that among other cookies "oauthenticator" one is the only one set with
HttpOnly: true
. This is the only reason I can think of to be invalidated since the expiration date for the cookie is one day ahead.This is the cookie state after the server sets up cookies :
Once Google authenticated a user and returns them back to JupyterHub, the
oauthenticator
cookie just disappears. Other cookies stay.I looked into jupyterhub/jupyterhub#2044 and jupyterhub/jupyterhub#1519, didn't help to understand how to fix this problem.
Hope someone can give a clue how to handle it.
Contents of
config.yaml
The text was updated successfully, but these errors were encountered: