https://supertokens.com/ logo
Join Discord
Powered by
Hey, I have 2 questions: 1) What do you mean with...
# support-questions-legacy
w
Hey, I have 2 questions: 1) What do you mean with: "You can also provide the table schema by providing the POSTGRESQL_TABLE_SCHEMA option." (https://supertokens.com/docs/thirdpartyemailpassword/custom-ui/init/database-setup/postgresql) ? I have users in public."Users" table ( and my url to db end on "?schema=public&sslmode=prefer". 2) I'm trying to add email verification. I want to use Sendgrid with domain, not smtp but I don't know how I should configure. How should I configure?
r
Hey @weboux
1) you don’t need to provide that config cause the default schema is public
2) see the email delivery section in docs. Specifically the custom method part.
w
2) I read but I don't understand,
r
I’m not sure how better to explain the concept than what’s in the docs
You need to override the sendEmail function to use sendgrid
w
so default POSTGRESQL_TABLE_SCHEMA is "public"?
r
Yes
w
If I write the function according to the Sendgrid documentation i.e. their Web API how will SuperTokens know that the user has clicked on the link? And how should I create this activation link to make it secure? I only know it must be dynamic.
I see.
r
The verification link is the input to the sendEmail function. You need to make an email template with that link and send via sendgrid.
When the user clicks on the link, it opens your frontend website and our pre built ui consumes the link
It’s all in the docs. Please have a look. I can only help answer very specific questions at the moment.
w
I see, so frontend sdk will see this link. I'll try to do this and if I'll have a problem I write again.
r
Sounds good
w
aaa and when I override sendEmail, backend sdk will see link too and add (and delete after click in link) to relevant table?
r
Yes.
w
I see. Thanks :)
aa I use custom ui, not prebuilt ui I forgot to write it😅
r
We have guides for custom ui email verification as well. Check those out
w
ah, I was reading in wrong place xd I need to override originalImplementation.sendEmail or sendEmail? in https://supertokens.com/docs/emailpassword/custom-ui/enable-email-verification#changing-the-email-verification-link-domain--path and whether if I have REQUIRED or OPTIONAL?
r
Yes
w
originalImplementation.sendEmail or sendEmail?
r
sendEmail.
You don’t need to call oroginalImplementation.sendEmail
w
I see.
Hey, I still have a problem. I have so: https://gist.github.com/jukialen/5197840d37023523007b9eabca7f0af4 now and I don't know what I do wrong.
I use Nestjs and prisma.
@porcellus Can you help me?
r
Hey. We can’t help unless you are specific in your question. Sorry
w
I want to override sendMail funcion to send email via Sendgrid and I need convey proprs to my sendMail function,
r
Custom props?
w
Yes. I have: templateVersion, verificationUrl and email.
r
So the verification url and email are part of the input itself
Template version, how do you determine that?
w
input.verificationUrl and input.email? I think, that 1 function for verification email and forgot password is good programiing idea. This is id for dynamic template id.
I have object with ids and I'll use in this props: template.someNameId
Do you understand? I was trying but I cannot do this (override with props).
Can you help me after these details? 😅
Now I have: override: (originalImplementation) => { return { ...originalImplementation, sendEmail(input) { return send({ templateVersion: templates.confirmEmail, verificationUrl: input.url, email: input.email, }); }, }; }, but I have this error: "TS2560: Value of type '(originalImplementation: any) => any' has no properties in common with type '{ functions?: (originalImplementation: RecipeInterface, builder?: OverrideableBuilder) => RecipeInterface; apis?: (originalImplementation: APIInterface, builder?: OverrideableBuilder) => APIInterface; }'. Did you mean to call it?" i ostrzeżenie: "Unused function sendEmail"
p
So as the first error shows, the sendEmail override shouldn't be there (on that level it should be an object). It's supposed to go inside the emailDelivery config. Please check out our docs: https://supertokens.com/docs/thirdpartyemailpassword/email-delivery/custom-method
w
I accidentally deleted "emailDelivery: {" xddd
Now I have so: ThirdPartyEmailPassword.init({ providers: [ ThirdPartyEmailPassword.Google({ clientId: process.env.GOOGLE_ID, clientSecret: process.env.GOOGLE_SECRET_ID, }), ], emailDelivery: { override: () => { return { // ...originalImplementation, sendEmail: async function ( input, ): Promise< | { statusCode: HttpStatus; message: string } | BadRequestException > { return send({ templateVersion: templates.forgottenPassword, verificationUrl: input.passwordResetLink, email: input.user.email, }); }, }; }, }, }), EmailVerification.init({ mode: 'OPTIONAL', emailDelivery: { override: () => { return { // ...originalImplementation, sendEmail: async function ( input, ): Promise< | { statusCode: HttpStatus; message: string } | BadRequestException > { return send({ templateVersion: templates.confirmEmail, verificationUrl: input.emailVerifyLink, email: input.user.email, }); }, }; }, }, }), Maybe now is ok? I only have errors with types.
r
If you have errors in types, you should fix them.
I’m sure you can figure it out. The docs are clear enough. Thanks
w
But this code already is ok? I should can fix types errors although they are strange.
r
I’m not sure if the code is ok. See our docs please.
w
I only mean if my function override is ok. My send function is another topic.
r
Seems fine. Test it out though
w
Yes. When I manage to fix the bugs with the types, I will test the whole authentication.
PreviousNext
Powered by