What could be causing the login to post to "http://localhost:3000/api/auth/authorisationurl?thirdPartyId=undefined&redirectURIOnProviderDashboard=undefined " when clicking on login with google/github? Nothing has changed with the code for a long time but it has decided to stop working

Hello everyone, does anybody encounter this error

{t: "2023-12-22T11:15:13.063Z", message: "middleware: Started", file: "/gateway/node_modules/supertokens-node/lib/build/supertokens.js:145:22" sdkVer: "16.6.5"}
2023-12-22T11:15:13.072Z com.supertokens {t: "2023-12-22T11:15:13.072Z", message: "middleware: Not handling because request path did not start with config path. Request path: /.well-known/jwks.json", file: "/gateway/node_modules/supertokens-node/lib/build/supertokens.js:152:26" sdkVer: "16.6.5"}

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?

im trying to get the logged in users email on the backend: const ThirdParty = require("supertokens-node/recipe/thirdparty"); async function generateNewInvoice(req, res, next) { const userId = session.userId; let userInfo = await ThirdParty.getUserById(userId); But it dies at the ThirdParty.getByUserId() method: Uncaught Error Error: Initialisation not done. Did you forget to call the SuperTokens.init function. Im following this guide basically exactly. What am I doing wrong? https://supertokens.com/docs/thirdparty/common-customizations/get-user-info#using-getuserbyid

Hi, I'm trying to implement supertokens with out ldap and AD servers. From my understanding I need to implement a custom provider. I'm just not sure from the example code given how that works? How do we get the client id and client secret?

@rp_st did you train the chatbot on the discord data?

Hi, I followed the nestjs setup guide and when I went to auth/dashboard it showed a server error. Nest app shows this error: SuperTokens core threw an error for a GET request to path: '/apiversion' with status code: 401 and message: Invalid API key. The connection uri and api key in nest are the ones provided in the managed service, I don't know what could be wrong.

Hey there, back with another few questions. 😇 I am planning the upgrade from

supertokens-core

v3.16.2

to

v4.0.0

and I have a few questions around the database changes for the

emailpassword_users

and

thirdparty_users

table: Why did you choose

VARCHAR(256)

and

VARCHAR(128)

over just

TEXT

? The latter would have required no database migration and would not require a database migration in the future if the value changes again. Is it safe for me to use

TEXT

instead of

VARCHAR(256)

- or does

supertokens-core

do some kind of database schema validation? How did you manage to roll this out in production? In my current understanding it is not possible to apply this migration without locking the full database table and rewriting every single row. Wouldn't it been smarter (and also less "breaking") to follow this strategy: 1. Add a new columns "thirdparty_users"."third_party_user_id_new" and "emailpassword_users"."password_hash_new" 2. Run a script during outside of a migration/lock that copies the values from the old column to the new column 3. Write the super tokens code in a way that it can deal with both the old and new columns for the duration of the copy from old to new column period Right now, for us running the migration will probably not take longer than a few seconds - however, I am concerned that in the future additional breaking database changes will make it harder for us to migrate to the latest versions. Since you probably have much more users running on your hosted solution, I am especially curious on any insights on how you manged this (of course only if it is possible to share that information)!

Hey, i got a little problem after enabling email verification at EmailPassword recipe.

javascript
EmailPassword.init({
  emailVerificationFeature: {
    mode: "REQUIRED"
   }
})

I noticed this every time when i signup successfully i received two email verification email instead of one. I started to digging why this is happened and i added the createAndSendCustomEmail option to my backend setup

typescript
EmailPasswordNode.init({
  emailVerificationFeature: {
    createAndSendCustomEmail: async (user, emailVerificationURLWithToken) => {
      console.log(user, emailVerificationURLWithToken);
    }
  }
})

The callback fired 2 times after every successful signup. I assume the root of the problem is with my frontend setup because it is the only one who is calling my backend. Do you have guys any idea what i did wrong ? 😅

Hi. for handing errors in typescript, is there any way to not have error in the catch block as an any type?

// eslint-disable-next-line @typescript-eslint/no-explicit-any
} catch (e: any) {
  if (e.isSuperTokensGeneralError) {
    ...