Hello, sorry to be a bother. I am setting up a 3rd party solution, and I have the button, can then get to the provider, sign in, and come back. This is where I am stuck. I can't figure out what I should come back to. No matter what I seem to do I just end up back on the signin page. Do I need to make a new express route to come back to and somehow set the login there? Or is there a specific supertoken url I'm supposed to come back to? I tried

[url]/auth/callback/[id]

along with many others. Nothing seems to run the

getProfileInfo

function or any other function I can find.

Hello everyone! I have a general question about SuperTokens, I like the idea of using it as an authentication server for my fairly large architecture with multiple services, but I'll also need the flexibility which I'm not sure it has. I'm wondering if those will be easy features to add or not, so in your experience, is SuperTokens easy to integrate with? https://supertokens.com/docs/thirdpartyemailpassword/advanced-customizations/apis-override/usage One example I have is that I want to expose some LDAP functions using LDAP.js and allow access to SuperTokens users, I will also use the new UserRoles recipe to get the LDAP functionality SuperTokens provides: https://supertokens.com/docs/nodejs/modules/recipe_userroles.html Furthermore, it would be great, if I could have more direct control over SuperTokens, for instance I want to create a certain user type with preset fields if they're coming from a specific tool, which means I could either override SuperTokens hooks, or what I would prefer to do is call a custom API method like

POST /auth/<user-type>

and then call a function from SuperTokens SDK to create that user: https://supertokens.com/docs/nodejs/modules/recipe_thirdpartyemailpassword.html#emailPasswordSignUp-1 Is this a good way to go about it? Also, how much data is recommended to be stored with the UserMetadata recipe? Should it only be for very simple structs or can I use SuperTokens to handle business data such as a paid subscription or personal data? https://supertokens.com/docs/thirdpartyemailpassword/common-customizations/usermetadata/about

Hey, I'm receiving the following error. (I'm working on macOS) RuntimeError: asyncio.run() cannot be called from a running event loop sys:1: RuntimeWarning: coroutine 'Supertokens.send_telemetry' was never awaited RuntimeWarning: Enable tracemalloc to get the object allocation traceback

Currently getting this issue:

Error: SuperTokens core threw an error for a GET request to path: '/apiversion' with status code: 401 and message: Invalid API key

Can't find any resources online to solve it. Running hosted supertokens in a dev environment. supertokens-node 16.7.1 supertokens-web-js 0.9.1

So I'm getting this error when calling `SuperTokens.init`: > Please provide a valid URL path This is my config

ts
SuperTokens.init({
  supertokens: {
    connectionURI: "http://127.0.0.1:3567",
  },
  appInfo: {
    appName: "SuperTokens Testing",
    websiteDomain: "http://localhost:3000",
    apiDomain: "http://localhost:3000",
    apiBasePath: "/auth",
  },
  recipeList: [
    EmailPassword.init(),
    Session.init(),
  ],
});

Any idea why I'd be getting this error? Seems like the URLs I have are valid.

I'm new to SuperTokens and wanted to get some questions answered about using it, with a transition from NextAuth to SuperTokens

Think I might have a bug report regarding user meta/the dashboard. I'm using ThirdPartyEmailPassword receipie in my FE and BE configs. And UserMeta/Dashboard in my BE config When I go to the dashboard to edit a users name and click save I get these logs:

Error: Initialisation not done. Did you forget to call the SuperTokens.init function?
at Function.getInstanceOrThrowError (/app/node_modules/supertokens-node/lib/build/recipe/emailpassword/recipe.js:199:15)
at /app/node_modules/supertokens-node/lib/build/recipe/dashboard/api/userdetails/userPut.js:76:18
at Generator.next (<anonymous>)
at /app/node_modules/supertokens-node/lib/build/recipe/dashboard/api/userdetails/userPut.js:30:75
at new Promise (<anonymous>)

But when I refresh the dashboard, the meta has actually saved

Hello, Sometimes i am getting the error

supertokens_python.exceptions.GeneralError: No SuperTokens core available to query

. Is this caused by network issues? (i am using the managed service)

Hey I am facing a issue with supertoken today, can someone help me out

{"statusCode":500,"error":"Internal Server Error","message":"SuperTokens core threw an error for a POST request to path: '/recipe/jwt' with status code: 500 and message: Internal Error\n"}

is someone aware about this error? i am using

"supertokens-node": "9.1.2",

version of super token and method which is throwing the error is

import Session from 'supertokens-node/recipe/session'
Session.createJWT(JWT, JWT_EXPIRE_TIME)

Hello, Thank you for your product, it’s amazing how simple and comfortable it is to set up and use. Your work is breathtaking 🙂 But there’s one issue I ran into. Can you help? I’ve set up supertokens-python on FastAPI(0.95.1), and now I keep getting exceptions:

h11._util.LocalProtocolError: Can't send data when our state is ERROR

It seems that the root cause for it is inheritance from Starlette's BaseHTTPMiddleware https://github.com/encode/uvicorn/issues/111 https://github.com/encode/starlette/issues/1678 Can you help me in rewriting your middleware so it doesn’t use BaseHTTPMiddleware? Specifically, I have no idea what to do with

python
if result is None:
    response = await call_next(request)