Having same issue

te sirvió?

Indeed. I’d suggest learning NextJS to anyone. Love it

took me minutes to this solution, Comment section == stackoverflow

Seems like the response didn’t contain a state. That’s most likely because your authorization url also had none

Use the syncronize option that comes with the clock of windows.

Most likely a synchronization issue, yeah

clock_skew_in_seconds = <int> id_info = id_token.verify_oauth2_token( id_token=credentials._id_token, request=token_request, audience=GOOGLE_CLIENT_ID, clock_skew_in_seconds=10 )

click on error details, they will give you the new URI to add, go to credentials page, select your credential, scroll down and add the given URI to it.

Your redirect uri does not comply with the standard. Maybe your redirect uri points to something like 0.0.0.0… or 127.0.01? However it must be a hostname e. g localhost

Use the syncronize option that comes with the clock of windows.

True, i fed up with errors, then went straight to his github and copy pasted his code, it ran sucessful 1 time... :D 1 time :D

"Agreed"

Thank you!

Amazing!

better solution is wraps because it mimics the function completely including docstrings. @functools.wraps(function) def wrapper(*args, **kwargs):

True

Check out this post: blog.miguelgrinberg.com/post/how-secure-is-the-flask-user-session . There are several solutions to this, such as flask-session, that rather saves data server than client sided e. G: pypi.org/project/Flask-Session/

@@code_specialist thanks

In the step of the callback we create an object „id_info“ that contains user information provided by Google by default. It also contains an „email“ field. There should also be something like an „email_verified“ field. However, that requires the scope to be „profile“ and „email“ at least. Our example already set those scopes. Check developers.google.com/identity/sign-in/web/backend-auth for more information

Up ittyhhjióp

P

I’m super late but any chance you could do a 3rd video on ci/cd and deployment? That’d be amazing!

@@Swingman23 Unfortunately the feedback and the number of views was underwhelming for this series, which is why we stopped this after the second video. What would you expect of a video covering CI/CD and deployment? Maybe we can create a short one for your specifics.

Miguel Grinberg whom we can recommend without reservation got an interesting article on the flask session: blog.miguelgrinberg.com/post/how-secure-is-the-flask-user-session . TLDR; the flask sessions are stored client side and not encrypted (basically they are just cookies). A valid alternative is the flask session library, which saves sessions server-side: pypi.org/project/Flask-Session/ . But there are also countless other solutions we didn't test personally. However, storing mere access tokens client side is common practice and is a valid production ready solution. The traditional flask session just isn't the right fit for any kind of sensitive data

Hu

That’s most likely due to cookies that save the state of your Google auth requests. To clear the sessions you have to delete the cookies related to your Google login. Most browsers offer an overview of cookies in their developer console. By default the shortcut is F12 in Firefox and Chrome.

Check out policies.google.com/technologies/cookies#types-of-cookies for more information on the topic

@@code_specialist Thank you for the immediate response.How to delete the google login cookies programmatically?

Flask offers a delete_cookie method on the response object. However, you may encounter difficulties as the cookie at hand isn’t yours. It’s also bad practice to touch cookies that ain’t yours.