Results 1 to 2 of 2

Thread: Multi Tenancy setup

Threaded View

Previous Post Previous Post   Next Post Next Post
  1. #2

    Default Re: Multi Tenancy setup

    Not a step by step but some pointers:

    It depends on how you want to manage your clients if your web application uses subdomains to differentiate between clients as in : https://learning.dataaccess.com/cour...bapps-on-urls/

    Then you need to get a wildcard certificate and have your customer add the wildcard domain record *.acme.com.au and point that to the customers web server.
    This way all traffic like: clientsite-a.acme.com, clientsite-whatever.acme.com etc. ends up at the web server.

    On the IIS side you can setup one website that does not use any hostheaders / SNI so all * traffic goes to that site. (usually this is the Default Website)
    If you have / create a second site for www.acme.com.au and set the hostheaders and enable SNI you will have one site that handles traffic for www.acme.com and the other site will manage the rest.

    (Hostheaders make it possible to have more websites running on one unique IP address and with server 2012 and up it becomes more easy to manage https sites too using SNI)

    Or you can create different sites in IIS with hostheaders and SNI and point them all to the same AppHTML (this gives a little more control)

    You might want to give https://learning.dataaccess.com/cour...ns-with-https/ a go too.
    Last edited by MI@DAE; 13-Jul-2020 at 03:32 AM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •