It is possible to disable the signUp component: You want to do the below on the frontend

EmailPassword.init({
  signInAndUpFeature: {
    signInForm: {
      style: {
        headerSubtitle: {
          display: "none", // this will hide the sign up button in the sign in form
        }
      }
    }
  },
  override: {
    components: {
      EmailPasswordSignUp: (_) => (_) => {
        return null; 
      }
    }
  }
})

You want to the below on the backend:

EmailPassword.init({
  override: {
    apis: (originalImpl) => {
      return {
        ...originalImpl,
        signUpPOST: undefined
      }
    }
  }
})

Also, just FYI, if you are using React components override and your custom component has some state, there is a bug in the lib which resets your state on tree rerender.. we are releasing a fix for this today.

@User ^

@User Thank you very much. I have everything I needed to have it work. (I will update lib - thanks) 🙂

Hello, are there any other providers other than GitHub, Google and Facebook for Supertokens?

there is apple as well, and we also have a way for you to define your own (fairly easily): https://supertokens.io/docs/thirdpartyemailpassword/common-customizations/signup-form/custom-providers

Understood, thank you.

If you do write a new provider, please consider contributing it back to the SDK 🙂

Yep, would surely do that.

Hi again, is the

user

scope the correct thing to ask here? Would asking just for the

user:email

scope not work? The issue being that asking for the whole user scope also gives the write permissions and not just the read.

is this for github?

Yes, the built in provider.

I'll have to have a look at the github docs for their scopes

cause we don't modify how the scopes you give are sent to github in any way..

But we don't give any scope for the built in providers right?

Only for the custom ones.

you can give for the built in as well.

I didn't find this mentioned anywhere in the docs. Could you share the link whenever possible.

yes

So you would use:

Github.init({
  clientId: ...,
  clientSecret: ...,
  scope: ["scope1", "scope2", ...]
})

Cool, thank you very much.

How can one obtain information like the first name, last name, and profile when using Google as a third party sign up option

@User , you need to use the override feature to have post sign up / in callbacks: https://supertokens.io/docs/thirdpartyemailpassword/common-customizations/handling-signinup-success#3-handling-signin-signup-event-on-the-backend If you see the code, you get

thirdPartyAuthCodeResponse

, which is the response that google returned which contains all the user's info (depending on the scope provided) + access and refresh tokens to query google's APIs.

The above works only for the node SDK >= v6.0.0

Hey, is there any known issue with ST-react in Safari? I am getting a weird

404

on

/api/auth/session/refresh

, during refresh session attempts. That's on the latest version.

This happens only on Safari?

Actually the 404 happens in every browser, but the other cascading behavior (not ST related) is only in safari.

In safari it errors saying headers already setn.

sent