I was trying to use my own email sending service for email verification, but not receiving any email, but the same script when used independtly works fine

Hello guys! I'm trying to test protected endpoints using postman. Sign in request works well, I get status Ok and user data, but..no cookies are updated in the Postman itself..So my next request to the API gets "message": "unauthorised". Is there any setting that I need to set to allow cookies? Or should I downgrade to a specific version of Postman? (Postman for Mac Version 10.11.2)

I am working on a frontend app talking to a supertokens backend and implementing OTP login with phone works like a charm, I wanted to read the JWT in the client so I had to add the session recipe to the backend and also call session.init in my client, this worked also like a charm and I was able to read the JWT. However when I do not log in using phone and OTP, I still want to have a JWT session for anonymous users but the Session.getUserId() returns false Is there anything more to it for session based authentication other than just having Session.Init() in the recipes array in the client and also in the backend? BTW: just wanted to shout out that other than this, using supertokens has been so smooth

Hi, I did get to /users and suddenly I'm getting this: " { "message": "invalid claim", "claimValidationErrors": [ { "id": "st-ev", "reason": { "message": "wrong value", "expectedValue": true, "actualValue": false } } ] } " after sign in (there are cookie there). What is this? I wasn't having this earlier. /users always worked and I checked auth: https://supertokens.com/docs/thirdpartyemailpassword/testing/testing-with-postman and I didn't change anything form this moment.

Hi, I'm looking to implement "web3" authentication. Is there anything like that integrating with SuperTokens already? If not, I would appreciate any pointers to the best way for me to implement it myself. (By "web3" auth, this is what I mean: on a new session the server sends a challenge to the user client who signs it with their crypto wallet and sends back to the server. The server compares the signed challenge with the previously registered public keys for the user. Here's an in-depth "vanilla" integration example https://www.toptal.com/ethereum/one-click-login-flows-a-metamask-tutorial)

Hi, I want to send magic link in the mail using different website domain. So is there any way in backend to fetch any website domain and send magic link using that particular domain? And also any way to send additional values from frontend to backend middleware API's.

Hi 👋 is there a way to add a username to the

smtp_settings

parameter? E.g. Sendgrid does require one.

If we use the supertokens connection uri, we wouldn't be able to modify the database to create new tables etc. This means that I have to "copy" the user id and email to my app's database, resulting in redundant information and possibly out of sync. What is the recommended action here? Why wouldn't ST let us have the db connection for prod just like for dev?

Hey, I have a sveltekit frontend and nestjs backend and I have figured out how to use supertokens on nesjs and sveltekit client side, but I don't know how to authorise on the server side and also how can I make API calls to my nestjs backend from server side in sveltekit, for ex in load function?

Hey guys. I had a question about the sendPasswordResetEmail method that we use to send a reset password link to the user. Can someone explain the different options available for how the email is sent? I checked the docs here https://supertokens.com/docs/web-js/modules/recipe_emailpassword.html#RecipeFunctionOptions but it isn't clear to me what the RecipeFunctionOptions object passed to recipe functions represents. Maybe an example of the options object and what it means can be helpful.