Getting Authorization Code from redirect URI (using Convex Auth w/ Google Provider)
Hello! I am using Convex Auth and have followed the steps to configure the signIn, signOut and other library functions. Now, for my use case, I want to access the Google Calendar API, to which I need the Authorization Code, which I will ultimately use to get an access token. However, I'm having trouble 'intercepting' the redirect so I can extract the authorization code from it.
As you see in the image attached, after the user gives consent, it redirects from the Google consent screen to the Convex redirect URI with a code as one of the parameters and then back to our frontend which is at localhost:5173 along with a different 8 digit code that Google doesn't support. How can I go about getting the code in the parameter of the redirect URI?
Thank you!
2 Replies
Thanks for posting in <#1088161997662724167>.
Reminder: If you have a Convex Pro account, use the Convex Dashboard to file support tickets.
- Provide context: What are you trying to achieve, what is the end-user interaction, what are you seeing? (full error message, command output, etc.)
- Use search.convex.dev to search Docs, Stack, and Discord all at once.
- Additionally, you can post your questions in the Convex Community's <#1228095053885476985> channel to receive a response from AI.
- Avoid tagging staff unless specifically instructed.
Thank you!
Welcome! The short answer is it's not supported. The code param should be present here: https://github.com/get-convex/convex-auth/blob/a52c18e31afaf49ceeea84ca0529df92cdb4304b/src/server/implementation/index.ts#L307
But it's not actually used for the auth flow as Convex Auth isn't accessing Google API's, so I believe it's just not being referenced at all.
In researching this, though, I learned providers like Google don't play nice with requesting this kind of access during sign in, it apparently causes issues. The recommended approach is to sign up and then request additional scopes. As with many extendend functionality requests for Convex Auth, I have to recommend looking to Clerk for this - they support requesting additional scopes: https://clerk.com/docs/authentication/social-connections/overview#request-additional-o-auth-scopes-after-sign-up