With the newer Core versions of ASP.NET Zero if you want to have non-login landing pages for your SaaS product you now need to use a multi-domain approach. Why this approach? I cannot think of any SaaS businesses out there where their business is divided up into multiple domains. I want to brand only one domain name, and have only one domain name. I don't want my landing pages/business information/sales pages on one domain name, and then my SPA on another domain name... that makes no sense to me and could confuse my customers. Are there any examples of SaaS businesses structured that way out there? I have never seen any such examples.
Can anyone suggest what steps are required to put things back to customer arrives at mydomain.com, can visit About page and Home page and learn about my Saas, and sign up, and then login to SPA that is maybe at mydomain.com/myspa, and I don't need to redirect them to myseconddomain.com for the SPA??
1 Answer(s)
-
2
Multi-domain approach is provided as a convienent way for the tenant account to login without typing and selecting the tenancy themselves.
It is done via DomainTenantResolveContributer. You can add/remove contributers from Configuration.MultiTenancy.Resolvers. See documentation
You can configure the landinng site (e.g public project) at www.mydomain.com and your application (e.g angular project) at app.mydomain.com then endpoints (e.g. Host project) at api.mydomain.com
