https://supertokens.com/
Join Discord
I just posted to production. Been developing localhost with nextjs. When in production I'm getting t...
f

funk101

over 3 years ago
I just posted to production. Been developing localhost with nextjs. When in production I'm getting this error:
has been blocked by CORS policy: Response to preflight request doesn't pass access control check: Redirect is not allowed for a preflight request.
I'm wondering if it has something to do with
NextCors
middleware? Any ideas?
f
a
r
  • 3
  • 213
  • 56
I am setting up something wrong with supertoken and I have no clue how to fix this? Does anybody hav...
s

Sekai

almost 2 years ago
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.
s
r
  • 2
  • 13
  • 55
Hi, I'm using multi tenants and wanted to share the session accros sub domains. So i referred here;...
z

zafer7929

almost 2 years ago
Hi, I'm using multi tenants and wanted to share the session accros sub domains. So i referred here; https://supertokens.com/docs/emailpassword/common-customizations/sessions/share-sessions-across-sub-domains But the example there uses the prebuilt UI (
supertokens-auth-react
), and i'm using my custom UI (
supertokens-web-js
) How can i accomplish sharing session across domains with the custom UI? Thank you
z
r
b
  • 3
  • 38
  • 55
I was working supertokens with React and Django rest framework. I have added super tokens for both r...
m

meseret_14335

over 2 years ago
I was working supertokens with React and Django rest framework. I have added super tokens for both react and Django rest framework but I can't sign up or sign in. When I click sign up with Google it says "Something went wrong. Please try again.". And here is the error message : "GET /auth/authorisationurl?thirdPartyId=google&redirectURIOnProviderDashboard=http%3A%2F%2Flocalhost%3A3000%2Fcallback%2Fgoogle HTTP/1.1" 200 281. can you guys help me
m
r
  • 2
  • 33
  • 55
Getting invalid api when curling to create a dashboard user with supertokens server -> curl --locati...
k

kiesker

over 2 years ago
Getting invalid api when curling to create a dashboard user with supertokens server -> curl --location --request POST 'Server link' \ --header 'rid: dashboard' \ --header 'api-key: ' \ --header 'Content-Type: application/json' \ --data-raw '{"email": "","password": ""}'
k
j
  • 2
  • 9
  • 55
Hey, there is a way to append ST tables to existing database? I used prisma ORM and im not sure how ...
d

damian_w

about 3 years ago
Hey, there is a way to append ST tables to existing database? I used prisma ORM and im not sure how can i update my migration to append ST tables
d
r
b
  • 3
  • 8
  • 55
Hello. I'm getting started on supertokens. How much memory is necessary for a the service database ?
s

sr.amorzinho

almost 2 years ago
Hello. I'm getting started on supertokens. How much memory is necessary for a the service database ?
s
r
  • 2
  • 3
  • 54
Hi <@498057949541826571> Looks like the front end module of supertokens tries to call the core in ...
a

aquamarine2620

over 2 years ago
Hi @rp_st Looks like the front end module of supertokens tries to call the core in a loop, it's making many calls per seconds without an end.
a
r
  • 2
  • 4
  • 54
question about FB login we used to use `getThirdPartyAuthorisationURLWithQueryParamsAndSetState` fro...
i

idanto

over 2 years ago
question about FB login we used to use
getThirdPartyAuthorisationURLWithQueryParamsAndSetState
from
'supertokens-auth-react/recipe/thirdpartypasswordless'
but after upgrade to the latest package version we are getting in runtime the error:
TypeError: Cannot read properties of undefined (reading 'startsWith')
    at appendQueryParamsToUR
I see in the docs this is the reference example:
import { getThirdPartyAuthorisationURLWithQueryParamsAndSetState } from "supertokens-web-js/recipe/thirdpartypasswordless";
is this the reason for the error or we are doing something else wrong?
i
r
  • 2
  • 64
  • 54
I am running supertoken using self-hosted core. I want to run both my auth server (nestjs) and auth ...
r

rangrik

over 2 years ago
I am running supertoken using self-hosted core. I want to run both my auth server (nestjs) and auth core using docker-compose. The issue is I am not able to pass the connectionURI of the core to the server. my authcore service is named -
authCore
so I tried passing
authCore:3567
but this doesn't work I see following error -
Error: Please provide a valid domain name
    at normaliseURLDomainOrThrowError (/app/node_modules/supertokens-node/lib/build/normalisedURLDo

    at new NormalisedURLDomain (/app/node_modules/supertokens-node/lib/build/normalisedURLDomain.js

    at /app/node_modules/supertokens-node/lib/build/supertokens.js:350:39
    at Array.map (<anonymous>)
    at new SuperTokens (/app/node_modules/supertokens-node/lib/build/supertokens.js:348:24)
    at Function.init (/app/node_modules/supertokens-node/lib/build/supertokens.js:372:36)
    at new SupertokensService (/app/src/auth/supertokens/supertokens.service.ts:15:17)
    at Injector.instantiateClass (/app/node_modules/@nestjs/core/injector/injector.js:358:19)
    at callback (/app/node_modules/@nestjs/core/injector/injector.js:59:45)
    at Injector.resolveConstructorParams (/app/node_modules/@nestjs/core/injector/injector.js:139:2
r
r
  • 2
  • 10
  • 54
Previous161718Next

SuperTokens.com

SuperTokens is an open source authentication solution offering features like: Different types of login: Email / password, Passwordless (OTP or Magic link based).

Powered by