core icon indicating copy to clipboard operation
core copied to clipboard

No way to renew Google Credentials

Open borpin opened this issue 10 months ago • 13 comments

The problem

If you have Google API credentials setup and you need to change them, there is no way to do it - the setup jumps straight to the page redirect.

What version of Home Assistant Core has the issue?

core-2024.12.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Gmail and Google Calendar

Link to integration documentation on our website

https://www.home-assistant.io/integrations/google_mail/

Diagnostics information

I have previously had a working integration of Google mail. I had to change the API credentials and now I need to renew the credentials in HA.

I have ended up with the integration not showing on the integrations list.

When I try and recreate the integration, the setup jumps straight to the page redirect without any means of changing the credentials. This of course fails as the credentials are no longer valid.

I think when the integration is no longer present, the credentials are retained, but I cannot find where.

Image

Image

Example YAML snippet


Anything in the logs that might be useful for us?


Additional information

No response

borpin avatar Feb 02 '25 14:02 borpin

Hey there @tkdrob, mind taking a look at this issue as it has been labeled with an integration (google_mail) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of google_mail can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign google_mail Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


google_mail documentation google_mail source (message by IssueLinks)

home-assistant[bot] avatar Feb 02 '25 14:02 home-assistant[bot]

The exact same thing happens to me when connecting to Google Calendar. Feel free to contact me if more details or tests are needed to fix this behavior!

hscheele avatar Feb 05 '25 14:02 hscheele

I started a community thread https://community.home-assistant.io/t/google-calendar-authentication-issues/763733

borpin avatar Feb 05 '25 15:02 borpin

https://my.home-assistant.io/redirect/application_credentials/

You can remove them here.

(Also borpin, we are still looking for your discord username as codeowner of emoncms, mind sending me a message?)

joostlek avatar Feb 05 '25 15:02 joostlek

Thanks joostlek, that was helping. After deleting the old credentials, all went through properly!

https://my.home-assistant.io/redirect/application_credentials/

You can remove them here.

(Also borpin, we are still looking for your discord username as codeowner of emoncms, mind sending me a message?)

hscheele avatar Feb 05 '25 16:02 hscheele

Also borpin, we are still looking for your discord username as codeowner of emoncms

@joostlek I have hopefully sent it on Discord. My usual one had gone IIRC.

You can remove them here.

Thanks. Seem to remember I have found that previously. ~~Can that be added to the documentation, please (or made more prominent if it is there :) )?~~ - Blind as a bat!

Also, for future reference, how do I navigate to them?

But it doesn't solve the issue. Perhaps the pop-up that has the 'Go to Web Page' link should also have a link to that credentials page?

borpin avatar Feb 06 '25 07:02 borpin

Screenshot_20250206-085658.png

joostlek avatar Feb 06 '25 07:02 joostlek

Ah, OK, hidden under the 3 dots. Should have guessed :(

Image

As I say, doesn't completely solve the problem as the dialogue should have a link to that when issues occur.

borpin avatar Feb 10 '25 08:02 borpin

What dialog do you mean?

joostlek avatar Feb 10 '25 09:02 joostlek

What dialog do you mean?

When trying to add/connect the integration (and there is an issue with the credentials), the add process jumps straight to the google site, which throws the error above. If you close that error page and go back to the HA integrations page, there is a dialogue box on the integrations page that has a button that says (something like) Go to Web Page. If you click that button, it takes you to the google page that says there was an issue.

The dialogue with the button, really needs an alternative link to the credentials page that says something like "If there is an issue with the credentials, delete them here (link) and try adding the integration again".

Unless you know where the credentials are, they are difficult to find 😄

If you delete the integration, should the credentials be deleted as well?

When adding other Google integrations, being able to select existing credentials would be useful (assuming you have set the credentials up in that way).

borpin avatar Feb 10 '25 11:02 borpin

The downside of that dialog, is that its just a generic dialog for launching an external page. This can be oauth, but also other Auth methods.

Fun fact: when Deleting the old config entry, you do get the question if you want to keep the old credentials

joostlek avatar Feb 10 '25 11:02 joostlek

Fun fact: when Deleting the old config entry, you do get the question if you want to keep the old credentials

AH OK, I'd forgotten that.

Shame about the dialogue.

So is the only way to update credentials, to delete the integration and credentials and recreate from scratch? Would this then require any automations etc to be recreated/edited? Is there no way to provide the ability to update credentials?

borpin avatar Feb 10 '25 11:02 borpin

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.