https://supertokens.com/
Join Discord
Hey 👋 I'm trying to authenticate via Google using the ThirdParty recipe. We're using NextJS only ...
c

cheerful_lemur_45830

about 2 years ago
Hey 👋 I'm trying to authenticate via Google using the ThirdParty recipe. We're using NextJS only for the frontend, NestJS for the API, and self-hosted SuperTokens core. The
authorisationUrlGET
request runs successfully but the
signInUpPOST
request receives a 500 in the frontend, and a 401 in the backend. The backend error message is just "Request failed with status code 401". We've successfully used the passwordless recipe with this setup so unsure why Google OAuth is not working. Any ideas?
c
r
  • 2
  • 3
  • 30
Hi, do you support managed solution implementation?
w

whatabout_79947

about 2 years ago
Hi, do you support managed solution implementation?
w
r
  • 2
  • 2
  • 30
Did anyone set up Nuxt 3 + Supertokens? Any thoughts how to stay on SSR? Saw only NextJS in guid...
w

whitekotenok

over 2 years ago
Did anyone set up Nuxt 3 + Supertokens? Any thoughts how to stay on SSR? Saw only NextJS in guides
w
r
  • 2
  • 1
  • 30
Hi, does supertokens support mechanism for device recognition? example use case: detect when an user...
c

czalez17

over 2 years ago
Hi, does supertokens support mechanism for device recognition? example use case: detect when an user login happens from a different device. If it does, can you please point me to documentation about it?
c
r
  • 2
  • 1
  • 30
I'm getting an error saying ""Are you sending too many / too few formFields?" I'm following the exam...
m

miguelstevensbe

over 2 years ago
I'm getting an error saying ""Are you sending too many / too few formFields?" I'm following the example from the docs, this is my frontend and backend code, am I missing something? ( I checked, the values are populated with data when sending the request to ST) frontend code
const response = await EmailPassword.signUp({
        formFields: [
            {
                id: "invite",
                value: invite.value.id
            },
            {
                id: "password",
                value: password,
            },
            {
                id: 'first_name',
                value: firstname
            },
            {
                id: 'last_name',
                value: lastname
            },
        ]
    });
And the backend
EmailPassword.init({
                signUpFeature: {
                    formFields: [
                        {id: "invite"},
                        {id: "password"},
                        {id: "first_name"},
                        {id: "last_name"},
                    ]
                },
                override: {
                    apis: (originalImplementation) => {
                        return {
                            ...originalImplementation,
                            signUpPOST: async function (input) {
                                if (originalImplementation.signUpPOST === undefined) {
                                    throw Error("Should never come here");
                                }

                                let response = await originalImplementation.signUpPOST(input);
                                console.log(input)


                                return response
                            }
                        }
                    }
                }
            }),
m
r
  • 2
  • 5
  • 30
Hi. Is there any way to change expiration time of tokens depending on the way session created? Now u...
k

kuzyaross

almost 3 years ago
Hi. Is there any way to change expiration time of tokens depending on the way session created? Now user gets its session using
auth/signinup/code
, then sends otp (we use passwordless recipe)
auth/signinup/code/consume
which gives them tokens. This works fine, but now we want users of mobile app, which we are developing have tokens which will expire after a day, not after several hours as now. TIA.
k
n
  • 2
  • 17
  • 30
Hi, I have a problem with signing up into my self-hosted backend. I was following instructions in ht...
n

nisky_man

over 3 years ago
Hi, I have a problem with signing up into my self-hosted backend. I was following instructions in https://supertokens.com/docs/emailpassword/quick-setup/backend. I am using Angular application, and I'm trying to integrate SuperTokens into my app. My backend is in the same project as the main app, could this be a problem? Thanks for help in advance!
initinit
n
r
  • 2
  • 4
  • 30
Hi team I'm running into a new CORS error we haven't had in the past. The CORS configuration is now ...
l

lmac3959

over 3 years ago
Hi team I'm running into a new CORS error we haven't had in the past. The CORS configuration is now blocking requests between our api (express) and client (react) with the error message: "Access to fetch at 'https://vms-api.macleanengineering.com/auth/signin' from origin 'https://vms.macleanengineering.com/' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled." We've set out cors configuration according to the user/password user guide so I'm starting here. Here's our current cours config: app.use(cors( { origin: ['https://vms.macleanengineering.com/'], allowedHeaders: ["content-type", ...supertokens.getAllCORSHeaders()], credentials: true, } ));
l
r
  • 2
  • 56
  • 30
I get error - Please call the supertokens.init function before using SuperTokens even if I call this...
d

Deleted User

over 3 years ago
I get error - Please call the supertokens.init function before using SuperTokens even if I call this function with all required arguments. Does anybody have idea why this would happen?
d
r
  • 2
  • 12
  • 30
I discovered today that Playwright might give devs access to the browser's cookies. (Would have to c...
i

ITEnthusiasm

over 1 year ago
I discovered today that Playwright might give devs access to the browser's cookies. (Would have to confirm on my own.) If they do, it could be a great tool for testing example repositories since it also enables devs to disable JavaScript in the browser during end to end testing. If a set of standard test cases could be created, they could be run against any example repo to make sure everything still works as expected during repo NPM package upgrades, etc. Hoping to look into this sometime within the next 4 months. But sounds pretty exciting (since it would take away a lot of manual work).
i
  • 1
  • 2
  • 29
Previous434445Next

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