Hi guys! I´m trying to understand how to get third-party user´s first and last name... I´ve enabled metadata feature and added scope https://www.googleapis.com/auth/userinfo.profile to google provider - but those fields are not set. Please suggest what I´m doing wrong?

hey @artico you need to set those manually in the user metadata recipe.

thanks @rp , but how do i get them? is there an example gist or something?

which recipe are you using?

ThirdPartyEmailPassword

See this: https://supertokens.com/docs/thirdpartyemailpassword/common-customizations/getting-provider-access-token

ok, and after "let accessToken =..." i have to call google api to get the names, right? and the same goes to apple as well?

yes

thank you! by the way, under the hood supertokens use the new Google Identity Services for Web solution, or rely on the old Google Sign-In JavaScript platform library for Web is set to be deprecated after March 31, 2023 ?

@sattvikc can answer this.

will get back in a moment

i use nest.js

and about the google identity service, we don't use the javascript platform library. we use standard open-id/oauth2 approach.

@sattvikc if i´d like to work with both google and apple in the same override, i have to distinguish them by input.provider.id, right?

right

i have success with google, by change do you have time to give me apple example, please?

scope should be an array, plz set it to ['email', 'name']

@sattvikc i set it to array for both google and apple, however resulting URLs differ: https://accounts.google.com/o/oauth2/v2/auth/oauthchooseaccount?scope=email%20profile... https://appleid.apple.com/auth/authorize?scope=email+name... google's one seems right, but apple's not. not sure where this happens, maybe on supertokens side which makes the redirect

+ and %20 mean the same in the URL

hey @artico - unfortunately we won't be able to help you with the name issue with apple at the moment. You can try and solve it yourself using our overrides feature. That being said, we are working on fixing this issue entirely in our SDK and will release this in 1-2 months time

@rp ok i will try.. please suggest how can i get original apple response in the override function?

You need to use your own apple keys and can set the callback url on your side

@rp if i specify my own redirect URI - what is the default path on my own supertokens setup to handle that? or this handler exists only on your site?

It will be your apiDomain/auth/callback/apple

thank you @rp ! and the last question: is it possible to get request data from apple using override or i have to fork and modify source code for that?

You can get the request data. It should be available in the input.options.req object (if you are using node SDK)

@artico did you get this working? I do not see the value in the input.options.req object. I'm calling both getFormData and getJSONBody and don't see it in either. I think the second post is overriding the value. I see a POST to /api/auth/callback/apple and then another to /api/auth/signinup and I can only retrieve the values from the second.

Perhaps @sattvikc can help here.

may I see your supertokens init and overrides ?

I've successfully found the value! Is there a recommended way to pipe it to the actual signinupPOST flow?

appleRedirectHandlerPOST: async function (input) {
                                console.log("REDIRECT INPUT", input)
                                let result = await originalImplementation.appleRedirectHandlerPOST(input)
                                console.log("REDIRECT RESULT", result)
                                let data = await input.userContext?._default?.request?.getFormData() // [Object: null prototype]
                                let user = { ...data }.user
                                console.log("REDIRECT USER", user)

                                return result
                            }

Hi @Davido, there is no recommended way to pipe it as of now. for now, you could write your own redirect to the frontend and include the data in that. And then the signInUpPOST will also need some tweaking to be able to send that information again. We are working on new interfaces to be able to do this easily. but, that will take some time to release.

Thanks! I'll take a closer look at those options