adding a domain to the "Approved JavaScript Origins" of the OAuth 2.0 Client ID

I would like to know the impact of adding a domain to the "Approved JavaScript Origins" of the OAuth 2.0 Client ID.

I want to add my domain to the "Approved JavaScript Origins" of my OAuth 2.0 Client ID.

The target OAuth 2.0 client ID is currently being used by a web application on another domain and is in production.

If I add a new domain to the "Authorized JavaScript origins" for an OAuth 2.0 client ID that is already running on another domain,
Is it possible that the API cannot be executed during that time because the target OAuth 2.0 client ID is in Google's re-examination status?

I'm in trouble if a situation occurs where API linkage is not possible with a web application on an existing domain.

1 0 299
0 REPLIES 0
Top Labels in this Space