cancel
Showing results for 
Search instead for 
Did you mean: 

Updating account linking on Google Smart Home Action (cloud-to-cloud

mgmarino
Community Member

Hi all,

We have a google smart home action (cloud-to-cloud) that has been in production for years. We would like to update the account linking (i.e. point to a different OAuth2 server).  The process to update seems relatively clear but what is not so clear is what happens to the users on the *current* action once it is updated? Do they continue going to the old endpoints for the refresh token until they relink, or will they immediately start using the new endpoints in their action?

 

Thanks for your help!

2 Recommended AnswerS

Suc1
Solutions Expert
Solutions Expert

When updating your OAuth2 server for a Google Smart Home Action, existing users will continue using the old endpoints for refresh tokens until they manually relink their accounts. The update doesn't automatically migrate existing users to the new endpoints. Users will need to go through the account linking flow again to switch to your new OAuth2 server.

View Recommended Answer in original post

mgmarino
Community Member

Replying to my own question. Our information from the HA certification is the following:

It seems you are going to update the account linking setting in this new submission. We will overwrite the original Client ID/Client secret, and this will unlink all existing users. Users have to relink to your integration and relink all devices. Please knowing this possible influence and notify the users before making updates.

Our request for clarification on this, i.e. whether or not we can do any sort of migration was simply the following:

> It will force to unlink all existing users. Users have to relink to the integration and relink all devices.

 



As such, I do not believe the answer from @Suc1  is correct.

View Recommended Answer in original post

3 REPLIES 3

Suc1
Solutions Expert
Solutions Expert

When updating your OAuth2 server for a Google Smart Home Action, existing users will continue using the old endpoints for refresh tokens until they manually relink their accounts. The update doesn't automatically migrate existing users to the new endpoints. Users will need to go through the account linking flow again to switch to your new OAuth2 server.

bosscathy
Community Member

the code to  turn alarm off

mgmarino
Community Member

Replying to my own question. Our information from the HA certification is the following:

It seems you are going to update the account linking setting in this new submission. We will overwrite the original Client ID/Client secret, and this will unlink all existing users. Users have to relink to your integration and relink all devices. Please knowing this possible influence and notify the users before making updates.

Our request for clarification on this, i.e. whether or not we can do any sort of migration was simply the following:

> It will force to unlink all existing users. Users have to relink to the integration and relink all devices.

 



As such, I do not believe the answer from @Suc1  is correct.