Many b2b apps allocate one subdomain per customer. For example, if my domain is
example.com, I may allocate one subdomain per customer like
client2.example.com and so on (
clientN can also be the client's name instead)...
In this case, there are two choices for architecting login:
One login, many sub domains: A site may have one login page on
login.example.comusing which all customers can signin / sign up. If
clientNsigns in, they will be redirected to
One login per sub domain: A site may provide one login per customer domain. So
clientNlogs in via
clientN.example.com/authand after signin, they are redirected to
SuperTokens supports both the methods. Please see the next pages to learn more.