-
-
Notifications
You must be signed in to change notification settings - Fork 178
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
Google Authorization Error #644
Comments
First, make sure you're using the latest version of the addon. Are you sure you're getting the "redirect_uri: urn:ietf:wg:oauth:2.0:oob" error when using the "simple" authorize button? That shouldn't be possible and it would mean I have a serious bug somewhere. As for using the local auth instructions, earlier this year Google changed how they allow authorization with their services. Here is their announcement for reference, though that announcement is so full of corporate buzzword bullshit it can't really be parsed in an understandable way. The gist of it it that if you authorized the addon using these custom credential directions prior to march 2022, they will stop working eventually. Most likely this is whats happening to you. To fix this you'll need to run through the directions again, taking note of the instructions I've added for people who had previously generated credentials (ie see the note under step 3). Again make sure the addon is up to date, as the addon also needed to be changed to handle the new authorization mechanism. |
Yes, I just tried the simple method and getting the error: using this button on my screenshot. I am also trying to change the Google drive account to a new account, the account was created no more than 3 weeks ago and the app authorization is also very recent, 3-4 days ago. I'll go through the instructions again and will recreate the app authorization to see if that helps. Also I am not sure what is the latest version but I have 0.99.0 and set to automatically update. ( I see a newer version on github than on my add-on but not sure if it's my add-on not updating or the new versions are not yet available for automatic updates) |
So, it appears that my auto-update was broken and didn't update for a very long time for some reasons (was stuck on 0.99.0), I uninstalled the add-on completely and reinstalled it and I was able to authorize the new Google account within the add-in using the simple method, not a single error or issue (now on 0.108.2). Thank you for all your work on this Stephen, this is in my opinion the most important add-on in HA. |
Hello, I have been using this add-on for over a year on my current setup and I am trying to change the Google drive account where my backups are saved but Google seems to be blocking something.
The currently configured account appears to still be working fine, the last backup was uploaded this morning at 3AM but when I try to change the account using both methods, I am receiving the same Google message when I get redirected to google to authenticate; (using the “authenticate with Google Drive” simple option) or authorize using client ID and secret (using the external domain method, fully configured on the new google account according to the instructions (https://github.com/sabeechen/hassio-google-drive-backup/blob/464a9e9c1bb362e247cb1411e8cab37183b09bed/LOCAL_AUTH.md)); I am always getting an Authorization Error from Google:
Authorization Error
Error 400: invalid_request
You can’t sign in to this app because it doesn’t comply with Google’s OAuth 2.0 policy for keeping apps secure.
You can let the app developer know that this app doesn’t comply with one or more Google validation rules.
Request Details
The content in this section has been provided by the app developer. This content has not been reviewed or verified by Google.
If you’re the app developer, make sure that these request details comply with Google policies.
redirect_uri: urn:ietf:wg:oauth:2.0:oob
Any ideas?
Thanks!
The text was updated successfully, but these errors were encountered: