Google's OAuth 2.0 - Authorization Error

[MartinMSPedersen]

• Found a bug

Details about the bug:

It is not possible to login using Google Auth.
It gives this error: "You can't sign in to this app because it doesn't comply with Google's OAuth 2.0 policy for keeping apps secure."

[welcome]

Welcome! 👋 Thanks for opening your first issue here! And to ensure the community is able to respond to your issue, be sure to follow the issue template if you haven't already.

[code4humanity]

@catarak, would you mind giving me some context to fix this issue?

[cwhetung]

Seeing the same issue here.

Cause: Using Google OAuth to login. Redirected to the failure page (PDF attached).

Closing Chrome completely and several retries sometimes let me in, but it is inconsistent.

p5js Sign in Error.pdf

Let me know what other info I can provide!

Thanks,
Clay

UPDATE Seems to work on Safari, but not always on Chrome Version 95.0.4638.69

[johhnry]

Hi,

Some users (including me) seems to have the same issue. Here is a linked thread on the Discourse forum:

https://discourse.processing.org/t/error-400-invalid-request/33288

[DavidGriswoldTeacher]

We are also having this problem. We did not have an issue until today. My students' projects are inaccessible until we get this fixed...

[DavidGriswoldTeacher]

Following up, I think I may know how to solve this problem.

The screenshot below is partially in English and partially in Portuguese (because I'm physically located in Brazil), so sorry about that.

When yo go to the Google help page for this error, one of the bullet points is shown below:

Since the web editor seems set up to use HTPPS just fine, my guess is that if the redirect URI is changed to https://editor.p5js.org/auth/google/callback in the google developer console, everything should work fine.

[catarak]

Hey all,

This has been fixed, and I'm sorry for not fixing this sooner. We're a really small team (in fact, the editor team is just me, part time), and there are a lot of notifications on discord/discourse/GitHub/Twitter/etc. It's difficult to sift through them and find that things that need to be attended to immediately. In the future, for anything urgent, please email [email protected]. And also, in the future, I'll do a better job of communicating how to reach the team for urgent issues. I really appreciate the patience and support!

[zeke]

Thanks for fixing this @catarak! We appreciate your hard work.