ellellell
07/16/2023, 10:01 AMthirdpartyemailpassword
for both frontend and backend config.
In what follows, ThirdPartyEmailPasswordReact
and ThirdPartyEmailPasswordNode
are just names for the default export from from supertokens-node/recipe/thirdpartyemailpassword
:
Frontend config fragment:
ts
ThirdPartyEmailPasswordReact.init({
useShadowDom: false,
signInAndUpFeature: {
providers: [
ThirdPartyEmailPasswordReact.Google.init(),
ThirdPartyEmailPasswordReact.Github.init(),
],
},
}),
SessionReact.init(),
Backend config fragment:
ts
recipeList: [
ThirdPartyEmailPasswordNode.init({
providers: [
// We have provided you with development keys which you can use for testing.
// IMPORTANT: Please replace them with your own OAuth keys for production use.
ThirdPartyEmailPasswordNode.Google({
clientId:
'1060725074195-kmeum4crr01uirfl2op9kd5acmi9jutn.apps.googleusercontent.com',
clientSecret: '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',
}),
ThirdPartyEmailPasswordNode.Github({
clientId: '467101b197249757c71f',
clientSecret: 'e97051221f4b6426e8fe8d51486396703012f5bd',
}),
],
}),
SessionNode.init(),
],
The only thing is that I have called supertokens with Userroles.init()
from a different server prior to calls from the UX. There's no userroles.init()
method available in the frontend supertokens-node/recipe/userroles
client package, afaics.
Screenshot of error: