Hi guys any example of declaring custom redirect uri while i

Question

Hi guys any example of declaring custom redirect uri while initialising third party providers in golang

rp · Answer

Hey < sattvikc> can help here

sattvikc · Answer

sure

sattvikc · Answer

< ggishant> you can do something like this let me know if u face any issues

ggishant · Answer

Thanks so much This was helpful

sattvikc · Answer

happy to help

ggishant · Answer

Also if we re using JWT what should be the key of the header on which we send the token I see that I have two tokens on the frontend namely Front Token and Id Refresh Token

sattvikc · Answer

< rp>

rp · Answer

You can send it with whatever key you like you will be consuming the token yourself somehwere

ggishant · Answer

I already implemented this able to intercept any query param but how do query for a specific provider

sattvikc · Answer

I m on it will let u know in a while

sattvikc · Answer

Let me know if this helps

ggishant · Answer

so do I have to maintain a mapping of my own with client ids and redirect uris for this

sattvikc · Answer

yes

ggishant · Answer

oh okay

ggishant · Answer

So the authurl endpoint returned the correct redirect uri but when redirecting to the server it added these scopes that I had in a different provider

ggishant · Answer

Also the endpoint gives me a 404

ggishant · Answer

```redirect uri web app = struct Params map string interface Params map string interface redirect uri Config GetEnvSecret BASE API URL + auth google webAppcallback var googleWebAppProvider = thirdparty Google tpmodels GoogleConfig ClientID Config GetEnvSecret GOOGLE CLIENT ID ClientSecret Config GetEnvSecret GOOGLE CLIENT SECRET AuthorisationRedirect redirect uri web app Scope default scopes IsDefault true ```

ggishant · Answer

this is how i registered the redirect uri

sattvikc · Answer

can u see what scope was returned with GetAuthURL API

ggishant · Answer

I think the scopes are all the scopes associated with that particular cloud console project

ggishant · Answer

the api returns correct scopes

ggishant · Answer

https accounts google com o oauth2 v2 auth access type=offline client id=218358531812 6vvp496o0qgnnr4q7nsph6gd55vjb17j apps googleusercontent com include granted scopes=true redirect uri=https 3A 2F 2Fishant app amigotest org 2Fauth 2Fgoogle 2FwebAppcallback response type=code scope=https 3A 2F 2Fwww googleapis com 2Fauth 2Fuserinfo email+https 3A 2F 2Fwww googleapis com 2Fauth 2Fuserinfo profile

sattvikc · Answer

are u getting those additional scopes on the callback from google

ggishant · Answer

yes

sattvikc · Answer

not very sure of that let me check

ggishant · Answer

these are the debug logs not sure why it says no recipe matched

sattvikc · Answer

callback is not handled by the backend

sattvikc · Answer

it s handled in the frontend and then there is a call to the SignInUp API

ggishant · Answer

but I m declaring the redirect uri on the backend

sattvikc · Answer

u mean are u specifying a backend url for the redirect uri

ggishant · Answer

yes should it be the website one and if it s the website one how will the frontend know do we need to specify it in the config as well for react

sattvikc · Answer

are you using our react sdk

sattvikc · Answer

it should be the website one supertokens react SDK will handle it there is no need to specify You also need not override the redirect URI it s automatically determined from the supertokens config

ggishant · Answer

yes

ggishant · Answer

Hi < sattvikc> < rp> is it possible to get on a short call struggling with a weird issue

ggishant · Answer

I m unable to redirect the user to auth endpoints on the frontend but am able to redirect to any other endpoint

sattvikc · Answer

on the frontend

ggishant · Answer

yes

sattvikc · Answer

< rp> can help

ggishant · Answer

if the code state is exchanged on the frontend doesn t that mean we have to store the client secret as well on the frontend

ggishant · Answer

if not then it must go to the backend but can t find an endpoint that does this

ggishant · Answer

or are we supposed to handle the callback on the backend ourselves and then register a user with provided functions from supertokens

rp · Answer

hey < ggishant> im available for a call now

rp · Answer

Join Zoom Meeting https us06web zoom us j 83472125568 pwd=WVZkYWxDZkZBY3hHSVFhemhLZ2M2Zz09 Meeting ID 834 7212 5568 Passcode 609355 One tap mobile +12532158782 83472125568 609355 US Tacoma +13017158592 83472125568 609355 US Washington DC Dial by your location +1 253 215 8782 US Tacoma +1 301 715 8592 US Washington DC +1 309 205 3325 US +1 312 626 6799 US Chicago +1 346 248 7799 US Houston +1 386 347 5053 US +1 564 217 2000 US +1 646 931 3860 US +1 669 444 9171 US +1 669 900 6833 US San Jose +1 719 359 4580 US +1 929 205 6099 US New York Meeting ID 834 7212 5568 Passcode 609355 Find your local number https us06web zoom us u kdrzVpprGw

rp · Answer

lmk when you can join

ggishant · Answer

hi i can join now

rp · Answer

ok

rp · Answer

sending new link the older one is invalid

rp · Answer

https us06web zoom us j 83125227130 pwd=dTV0RTRnVnNCTytPK3NUOHFhR0VUdz09

rp · Answer

hey < ggishant> as discussed please open an issue on our github highlighting the problem and what you want we will investigate this over the coming days

rp · Answer

< ggishant> we have fixed this issue in the latest golang SDK Now the open ID token will contain the user s profile info like their name and profile pic All you need to do is updated the backend SDK