Right now I'm doing a second call to the endpoint in the thirdPartySignInUpPOST section but really hate it. I'm looking to do the same thing with Apple "name" scope where I don't think I can go back to Apple as they only send it once (supposedly)
03/06/2023, 4:01 PM
So you send the auth code to the third-party (Google) a second time (using their APIs) and get the info that way?
03/06/2023, 8:52 PM
Sends the access token to third party to get info
We are reworking on this part of supertokens to provide you all the info upfront, including the name from apple.
03/06/2023, 11:10 PM
@Davido I came up with an approach that doesn't require a second load. Let me know if you're interested in hearing about it. I use
in my backend, so I'm not sure if it applies to you, but maybe it's worth a shot?
03/07/2023, 2:47 PM
Thanks, @dbottisti . I'm actually doing the id_token for google sign-in via js already but that's only one of my current paths.