I will try to get my front end developer

Thats where the auth will initiate from

Hope i can get what i want from supertokens

We integrate with your frontend and backend. So ideally both developers or one full stack Dev

Aslso what are the information i will need just in case supertoken wants me to have before our call

Just the tech stack you use and your auth use case.

Will try

3 types types of stacks: LAMP stack ( Linux , Apache, MySQL , PHP) For apps like nextcloud, rocket chat we are built in MERN stack ! Hope this helps

Understood. Thank you. Let's discuss this over a call - will be easier 🙂

Cool

Good night

Hi @User, I'm working with @User on integrating supertokens with fastapi. We got it working with the 2.x branch, but are wondering what the intended way of adding functionality to auth requests are (i.e. when someone signs up, we want to do something in our backend). Adding a fastapi route to the endpoint (i.e. /signup doesn't work). Thank you for you support!

@User , the route for sign up is /{baseApiPath}/signup POST. So the default is /auth/signup POST.

Since you have probably forked the repo, feel free to modify the sign up API logic that we have written to add your post sign up logic.

Also, did you use this branch? https://github.com/supertokens/supertokens-fastapi/tree/fastapi-2.x

the

fastapi-2.x

branch has APIs that are to be used by the auth widgets on the frontend. This was to be merged into branch 2.0 from our end, but we didn't do that cause we decided to write a supertokens-python repo instead. You should try using the code from that with the latest version of the core and frontend SDK.

Apologies for this confusion..

Thank you for your quick response! We forked

fastapi-2.x

as we fixed a minor bug. Our frontend/backend path is /auth/signup /auth/..., thus I was expecting that this handler gets called. Nevertheless, I got it working by specifying

handle_post_sign_up

like this

EmailPasswordRecipe.init(config={"sign_up_feature": {"handle_post_sign_up": handle_post_sign_up}})

which calls the method

async def handle_post_sign_up(a, b):

. Is this intended like this? Regarding versions: we're using

supertokens-core 3.4.1

and

supertokens-auth-react 0.14

> Is this intended like this? Yes.

Cool! So is there anything that you are stuck on at the moment @User ?

Awesome! 🙂 Two more questions for now: 1. Logging in with wrong credentials yields a WrongCredentialsException in the backend. This results in a CORS error in the frontend even though the CORSMiddleware is correctly configured. Even when I add a custom ErrorHandler to FastAPI and return a JSONResponse(200) I get the same CORS error in the frontend. Any ideas? 2. Password recovery via mail works, but email verification doesn't even though I add the EmailVerificationRecipe. No email is received.

> Logging in with wrong credentials yields a WrongCredentialsException in the backend. This results in a CORS error in the frontend even though the CORSMiddleware is correctly configured. Even when I add a custom ErrorHandler to FastAPI and return a JSONResponse(200) I get the same CORS error in the frontend. Any ideas? This is where we send the JSON reponse for wrong credentials: https://github.com/supertokens/supertokens-fastapi/blob/fastapi-2.x/supertokens_fastapi/emailpassword/recipe.py#L129. What is the CORS error that you get?

Regarding the second point, this is the API to send an email verification email: https://github.com/supertokens/supertokens-fastapi/blob/fastapi-2.x/supertokens_fastapi/emailverification/api/generate_email_verify_token.py Perhaps you could add some print statements there to see if it's called, and if it is, where it fails. The default implementation for

await recipe.config.create_and_send_custom_email(user, email_verify_link)

is here: https://github.com/supertokens/supertokens-fastapi/blob/fastapi-2.x/supertokens_fastapi/emailverification/utils.py#L31

Thank you so much for your quick responses @rp! 1. I got it fixed by moving the CORSMiddleware to the end of the file where FastAPI app was created 2. I'll look into the links you provided! Thanks 🙂

sounds good!

For the fixes you do, it would be great if you could create a PR into our repo :))

Hi, is an elixir/phoenix sdk planned? I saw a github issue for it but it didn't have any responses

hey @User , we don't have plans for that anytime soon, but you could build the parts you want by copying our node SDK: https://github.com/supertokens/supertokens-node, and the APIs: https://supertokens.io/docs/community/apis

Cool that's what I was planning on doing, really like the look of supertokens so far

thank you :)) What type of auth are you looking to use?