Can't auth by google account.... after access right in google to drawio app

[DarkNightHome]

Preflight Checklist

• [ ] I agree to follow the Code of Conduct that this project adheres to.
• [ ] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Describe the bug not auth in google account

To Reproduce Steps to reproduce the behavior: goto app.diagrams.net choose open in google drive doc... neet auth select google enter google account and pass give rights to app diagram.net.... see 401 error... not entered...

Expected behavior open chrome open google drive select open file in drawio and do auth and stuck

Screenshots If applicable, add screenshots to help explain your problem.

draw.io version (In the Help->About menu of the draw.io editor):

• draw.io version [e.g. 12.6.7]

**Desktop

• OS: Windows 10
• Browser Chrome
• Version

[xinatcg]

strange issue. I also get this issue on one of Google Account, but I try

1. another account, it works
2. incognito tab with this account, it works

I have tried to clean all Chrome data/ clean the cache storage of Google drive/ diagram.net, it should be totally clean on the chrome. but 401 still happen on the account.

[aisen0921]

Me too! But my error is a blank page.

[davidjgraph]

Clean cookies.

[xinatcg]

Clean cookies.

i have tried, actually, I clean everything I can clean on the Chrome

[xinatcg]

Clean cookies.

I think these cookies are what you mean if I am not wrong, I have tries lots of time

[davidjgraph]

No, it's the google domain cookies you need to clear, authenication is direct to google.

[xinatcg]

do you mean this?

[xinatcg]

No, it's the google domain cookies you need to clear, authenication is direct to google.

Or I need log out the google account from Chrome totally?

[xinatcg]

and I think the 401 error is the last step of Oauth right? https://app.diagrams.net use the token issued by Google to request the resource from google but Google refuses the request.

I think the most possibility is some information is not match the register app on Google Cloud, is it possible based on the network flow to find out the exact reason?

[davidjgraph]

I don't know exactly which cookie is the problem, but if incognito works, clearing all cookies will fix the issue. If someone could work out exactly which cookie is causing the issue, that would be useful.

[xinatcg]

I think there should be some issue here. I create a new chrome user and log in my google. the first time I connect to google drive successfully. but after a period of time, I try to open a diagram from the drive and ask me to authorise again. then the same 401 error.

[davidjgraph]

That's with all browser extensions disabled?

[xinatcg]

oh no, do you mean some extension make this error?

[xinatcg]

[davidjgraph]

The issue is originally about a complete failure of authenication, most likely caused by a cookie in a state that caused a problem. If you are seeing authenication timeout too quickly, that is likely another issue, please open another issue for it.

If it works incognito either an extension is causing the problem or a cookie. You need to clear cookies and switch off extensions one-by-one until the offending extension is found.

[rachelrlabare]

Hi - having the same issue. Cleared cookies, tried incognito and another browser and nothing has worked so far.

[xinatcg]

i use an extension session box to login make it works..

[davidjgraph]

If none of the solutions here fit, please open a new issue with details.

[Chazza011235]

I ran into the same problem as described by this ticket. After clicking the Authorize button and signing in, I got this generic error: The user account I signed in with is managed by Google Workspace (formerly known as GSuite). After much trial and error, it turns out that the solution is to turn on setting "Allow users to access Google Drive with the Drive SDK API" to the "Drive and Docs" settings in Workspace. So you may need to speak nicely to your Workspace administrator.

[pkgainwell]

Today it worked for me when I turned off this extension verint.dpa.chrome.trigger 15.2.9.144 Not sure if that is the sole reason.