Ok thanks.. So since I'll be using a chrome extension could I leave the websiteDomain as * ? appInfo: { appName: "CleanVid", apiDomain: "https://cleanvid-api.netlify.app", websiteDomain: "*", apiBasePath: "/.netlify/functions/auth", },

How to pass emailid in user context in passwordless login? when I pass emailid - it comes empty curl 'http://localhost:3002/auth/signinup/code/consume' \ -H 'Connection: keep-alive' \ -H 'sec-ch-ua: " Not A;Brand";v="99", "Chromium";v="98", "Google Chrome";v="98"' \ -H 'fdi-version: 1.8,1.9,1.10,1.11,1.12' \ -H 'Content-Type: application/json' \ -H 'rid: passwordless' \ -H 'sec-ch-ua-mobile: ?0' \ -H 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/98.0.4758.109 Safari/537.36' \ -H 'sec-ch-ua-platform: "macOS"' \ -H 'Accept: */*' \ -H 'Origin: http://localhost:3000' \ -H 'Sec-Fetch-Site: same-site' \ -H 'Sec-Fetch-Mode: cors' \ -H 'Sec-Fetch-Dest: empty' \ -H 'Referer: http://localhost:3000/' \ -H 'Accept-Language: en-GB,en;q=0.9' \ -H 'Cookie: sIRTFrontend=remove' \ --data-raw '{"userInputCode":"802331","deviceId":"urowSmkumH6t5DI/VMayKmM2sHmJdmjbAda6X/+2f3c=","preAuthSessionId":"PzcQXtL9_yC9bPrQCb68Ys5vCRPQQIwJG7YEdnkMnm8=","userContext":{"email":"prachi@xyz.com"}}' \ --compressed

Hey quick question. I thought I read it somewhere, but in the passwordless recipe, do the one time tokens only work when used at the device that caused the email to be sent?

Hey guys - where can I see what kind of user data is stored in the data?

Hey @rp_st we want to authenticate whether the client redirect URL is correct or not, if it is correct, then only we want to generate the accesstoken 1.can you show us is it possible or not? if yes, how? 2. does the supertoken store the client redirect url or not in their system? and if they do, what is the method from nodejs-sdk to verify the client redirect url?

When self-hosting, is there a good reason why not to run the core on the same server as the backend? I'm using a DigitalOcean droplet which will run my app backend, supertokens backend and I'm thinking why not run the core there too?

Hello! I want to setup domain for my app so I have added following NGINX configuration: location /auth { proxy_pass http://localhost:3567; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection 'upgrade'; proxy_set_header Host $host; proxy_cache_bypass $http_upgrade; } But when I open https:///auth I receive text "Not found" instead of "Hello" And when I start Node,js application I see error Error: SuperTokens core threw an error for a GET request to path: '/apiversion' with status code: 400 and message: AppId or tenantId not found => Tenant with the following connectionURIDomain, appId and tenantId combination not found: (, public, auth) When I open http://:3567/ everything works

@rp_st need support, when we deploy Supertoken core to decrease access token validity from 30 days to one hour, we've got this error:

jwt invalid: failed to deserialize token claims: could not get token claims: go-jose/go-jose: unsupported key type/format

that's happen when and after we deploy it. Any reason why?

Hello, i'm having an issue with the integration to NestJs. I'm getting a blank (white) screen when i try to load the dashboard... Everything seems to work fine when i call the signup api from postman though... Any ideas please?...

I am setting up something wrong with supertoken and I have no clue how to fix this? Does anybody have a clue? My first error in the console.log is this in the attached image.