• pogseal

    pogseal

    8 months ago
    thanks, will have a look
  • nahtnam

    nahtnam

    8 months ago
    Interesting, the oauth way would probably be the safest way to go. Have you thought about the feature request at all? I understand that there are much more important things to do but just wondering if you've thought of a solution. For example if you know that you will add oauth to support the feature then I'll just implement oauth on my end and swap it later
  • pogseal

    pogseal

    8 months ago
    another question. When setting things up for NextJS with multiple domains, I'm assuming only the ROOT domain needs the following? https://supertokens.io/docs/thirdpartyemailpassword/nextjs/setting-up-backend
  • pogseal

    pogseal

    8 months ago
    Whereas the subdomain sites can work fine with only the Frontend config?
  • r

    rp

    8 months ago
    We will add it for sure!
  • r

    rp

    8 months ago
    Yea. This is also assuming that the sub domains will be querying the root domain’s api layer.
  • pogseal

    pogseal

    8 months ago
    got it
  • nahtnam

    nahtnam

    8 months ago
    Great to hear. I was thinking of either setting up one supertokens per project OR one supertokens + oauth. I think I will go with OAuth because in the future, "Allow multiple apps to use the same set of users and login gateway." will mean only one supertokens instance so I will have less work in the future
  • nahtnam

    nahtnam

    8 months ago
    Thanks for your help!
  • r

    rp

    8 months ago
    Yea. It should be one supertokens instance for all projects.