Hello everyone can some share some repo showing implementation of supertoken with python django for social login without password using plain javascript in front end

How is the password verification enforced on the backend? Currently it is kind of only enabled via the frontend by setting the

emailVerificationFeature

option on the frontend? 🤔

SignInAndUp Component signUp view

I'm trying to setup the supertokens backend in NestJS and can't figure out, where to put the

connectionURI

and

apiKey

So this part:

ts
supertokens: {
        connectionURI: "http://localhost:3567",
        apiKey: "someKey" // OR can be undefined
    },

https://supertokens.com/docs/thirdparty/quick-setup/core/with-docker#connecting-the-backend-sdk-with-supertokens-

Hi there, can Supertokens work with Nextjs and Strapi?

Is there a way to do single sign out from the Thriparty IDP, once the app is logged out using signout method?

hey I implemented my project with supertokens and wanted to automate the backend site with a docker compose file. Everything works fine but the signup and signin routes are not. Any Ideas? I can provide logs

Hey, I was wondering if it's possible to remove the "Powered by SuperTokens" branding on the login and signup page. I'm using the hosted version admittedly still in the first 5000 users so not paying anything. But would happily pay to have it hidden.

async function doesSessionExist() {
    if (await SuperTokens.doesSessionExist()) {
      // user is logged in
      console.log("there is a session");
    } else {
      // user has not logged in yet
    }
  }

this returns error in react native

I have "staging" and "production". Production is set to "www.example.com" in appInfo(). So, "staging.example.com" is getting this error. I'm assuming this has to do with the "appInfo()" logic:

Access to fetch at 'https://www.finicky.pet/api/auth/session/refresh' from origin 'https://staging.finicky.pet' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: The 'Access-Control-Allow-Origin' header has a value 'https://www.finicky.pet' that is not equal to the supplied origin. Have the server send the header with a valid value, or, if an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.