Update Google Login to address "Inactive registered OAuth URIs" warning

AI-generated summary

Google will be removing inactive OAuth redirect URIs and JavaScript origins that are not compliant with their validation rules by July 12, 2021, and September 13, 2021, respectively. This affects Discourse sites using Google Login integration. To resolve the issue, review the project details and take one of the following actions:

  • Delete the project if it’s unused
  • Remove the old URL if it’s changed
  • Update the URL to https if it’s currently http-only, as per Google’s OAuth URI validation rules

If none of these cases apply, users can ask for help in this discussion.

Google has started sending out messages with the subject:

[Action Advised] Inactive registered OAuth URIs for your project(s) will be removed from Google Developer Console by July 12, 2021, for non-compliance with URI validation rules

And the leader:

We are writing to let you know that you have inactive OAuth redirect URIs and JavaScript origins in your Google Cloud project that are not in compliance with Google’s OAuth URI validation rules.

  • On July 12, 2021 , we will remove all inactive URIs that are invalid.
  • On September 13, 2021, we will remove all URIs that are not in compliance with redirect URIs and Javascript origins rules (including formerly inactive URIs trying to become active).

What do you need to do?

If you’re here, the URLs are likely referencing your Discourse site and this is your Google Login integration.

At the bottom of the email are details specific to your project such as:

If this project is unused (e.g. the site no longer exists), it can be deleted.

If the URL has changed since the project was set up and the old URL is unused, that URL can be deleted.

If the URL is http-only, it will need to be changed to https (as per the requirements linked above).

If it’s another case, feel free to ask about it here.

Last edited by @JammyDodger 2024-05-26T07:27:09Z

Check documentPerform check on document:
10 Likes