Hi, I'm trying to make login screen using OAuth 2.0 Client ID.
Since my application is multi-tenanted, I would like to define multiple login endpoints and redirect URIs e.g. `tenant1.example.com/api/auth/callback/google` , `tenant2.example.com/api/auth/callback/google` , etc.
So my question is: Does OAuth 2.0 Client ID in Google has limitation for amount of authorized redirect URIs?
I hope there is no limitation for this, but I should change strategy if there is limitation.
Hi @windymelt,
Welcome to Google Cloud Community!
The OAuth 2.0 doesn't specify a hard limit on the number of redirect URIs per client ID. However, some OAuth providers or identity platforms might have their own limitations or recommendations for the number of redirect URIs that can be registered for a client.
While there's no strict limit on redirect URIs for Google Client IDs, it's best practice to minimize the number of redirect URIs per Client ID. This is crucial for security, performance, and maintainability. If you have a multi-tenant application, creating separate Client IDs for each tenant is highly recommended.
For more specific information about Google's recommendations, refer to their OAuth 2.0 developer documentation.
I hope the above information is helpful.