Can I see your frontend and backend supertokens.init config?

problem is when you sign up with email and password, it redirect to verify-email endpoint

as opposed to images

backend

frontend

and the end problem is that in supertokens example with api it shows form and send email

but with my variant it doesn't do anything

p. s. i use export of FDI Api on backend

This is the component we are using to render the otp screen https://github.com/supertokens/supertokens-auth-react/blob/master/examples/with-emailverification-with-otp/src/OtpScreen/index.tsx

it says that cannot acces to the private variable of supertokens service

but in sendcustomemail i have not access to it by "this"

import { DynamicModule, MiddlewareConsumer, Module, NestModule } from '@nestjs/common'; import { AuthModuleConfig, ConfigInjectionToken } from './config.interface'; import { SupertokensAuthService } from './supertokens-auth-service/supertokens-auth.service'; import { SupertokensAuthMiddleware } from './supertokens-auth.middleware'; import { OtpService } from '../otp/otp.service'; @Module({ providers: [SupertokensAuthService, OtpService], exports: [], controllers: [] }) export class SupertokensAuthModule implements NestModule { configure(consumer: MiddlewareConsumer) { consumer.apply(SupertokensAuthMiddleware).forRoutes('*'); } static forRoot({ connectionURI, apiKey, appInfo }: AuthModuleConfig): DynamicModule { return { providers: [ { useValue: { appInfo, connectionURI, apiKey }, provide: ConfigInjectionToken } ], exports: [], imports: [OtpService], module: SupertokensAuthModule }; } }

Try adding a Content-Type: application/json header as well?

Thats a post operation to endpoint and error in response

So, where should i set content type application/json header?

Using swagger

recipe emailpassword works correctly but thirdpartyemailpassword does not work

you also need to pass in the sAccessToken

in the cookies

You need to stick to the same recipes on frontend and backend

@IaS1506 you tried the demo app from the other branch?

We are working on making account linking easier. But should take ~1-2 months.

)

But then i will be waiting for this)

If you register a user in email password, make sure to also verify their email before. If verification is not done, the account won't be linked.

can you help me with this, I just added all functionality, but user still creates without primary-user ...(

it will be difficult for me to go into your custom setup and help you out

And can i even do it

?)

And one another question: is there in your examples repository workable solution for integrating own reset password functionality?

Whilst you can cusotmise supertokens to use OTPs instead of links, you will have to store and manage the OTPs yourself.

But i had a schema for email verification, what i need to do to get workable solution in your examples

For reset password i have not found any of examples with it

So my problem is to know what i have to use to integrate it with myself

there will be equivalent functions related to reset password that you would need to override

but i see next screen

what should i override to see otpscreen instead?

this will allow you to change the form in which the email is entered, and the form which shows the above message in your screenshot

ok, sorry for lots of questions, but when i considered to use links (as your default variant) i get unathorized exception. It is logical, bc user does not have session when he is not logined, so how can i resolve it: create temporary session or you already had similar mechanism?

if you are using the token to reset a password

ah, it's my fault, sorry