Also is it possible to tweak the settings of the EmailPassword thingy ? like to change hashing algorithm and to directly supply a hash to the

ThirdPartyEmailPassword.emailPasswordSignIn()

?

hey @TeK it is possible to directly supply the hash. See our migration docs: https://supertokens.com/docs/thirdpartyemailpassword/migration/account-creation/user-creation You essentially want to call the API for migration like this:

curl --location --request POST 'http://localhost:3567/recipe/user/passwordhash/import' \
--header 'api-key: <API_KEY(if configured)>' \
--header 'Content-Type: application/json' \
--data-raw '{
    "email": "johndoe@example.com",
    "passwordHash": "$argon2d$v=19$m=12,t=3,p=1$NWd0eGp4ZW91b3IwMDAwMA$57jcfXF19MyiUXSjkVBpEQ"
}'

Ah there's no methods for it in the backend ?

not for this operation.

Uhm, i guess i'll send the password in clear then to my API, and how can i get the google auth url from the backend is it possible ?

> how can i get the google auth url from the backend is it possible ? Im not sure what you mean here.

I'm doing something like that basically. So i call this route from my Unity client to either login with email/password or get a google auth url and then after that it'll redirect to another endpoint for completing google login

you can see the API exposed by the backend SDK here and query them directly if you want: https://supertokens.io/docs/fdi

May i ask from where are those api endpoints in the sourcecode ?

auth/authorisationurl?thirdPartyId=google

do exactly what i want so i'd like to see how is it built

Thanks a lot, just as a last question, i'm sorry to annoy you. Is there a way to get the client session token after using the

ThirdPartyEmailPassword.emailPasswordSignIn

method ? this way i can return it to clients so they can use it next time for other requests ?

Can you ask this on a other thread? It’s not related to this thread’s topic