I have implemented Drive Picker for my web app to link the user's drive files.
But I have problem in pushing this feature to production because in OAuth2 Client I have to pass redirect_uri, but my clients/users have different domains, I cannot keep manually adding them in redirect_uri list.
Is there a way to overcome this blocker or any workarounds to accept dynamic domains?
Drive Picker Client side design has too many limitations.
Solved! Go to Solution.
You are asking in the Wrong forum
But I happen to. know about this topic and can tell you, yes, you need a distinct redirect uri for each registered client. That's for security. Avoiding that means breaking the OAuthV2 security model. It's not just a Google thing. It's for every OAuthV2 system.
More here: https://www.oauth.com/oauth2-servers/redirect-uris/
You are asking in the Wrong forum
But I happen to. know about this topic and can tell you, yes, you need a distinct redirect uri for each registered client. That's for security. Avoiding that means breaking the OAuthV2 security model. It's not just a Google thing. It's for every OAuthV2 system.
More here: https://www.oauth.com/oauth2-servers/redirect-uris/