I noticed that the Auth0 external id (

sub

) for the google provider was

google-oauth2|<ID>

. Now with supertokens I am building this within

createNewSession

, for mapping the accounts.

const externalUserId = user.thirdParty ? `${user.thirdParty.id}|${user.thirdParty.userId}` : null;

I noticed that

user.thirdParty.id

, here is

google

and not

google-oauth2

. Is it safe for me to simply replace the

google|

part with

google-oauth2

, is the

<ID>

part of the auth0 sub stable?

hey! yes it is fine to do that. But out of curiosity, why do you want to maintain that format? Is the logic in your application API relying on this type of format? Finally, we have a userID mapping feature as well which you can use to map supertokens userID to an externalUserId which is generally a better approach

see this commit: https://github.com/kamilkisiela/graphql-hive/pull/303/commits/04518a4c303a0e3b840be46409878cf38a241ebf

ahh i see

I am already looking forward when I can delete everything auth0 related from the codebase