Supporting Multiple URL for Service Provider

As a service provider, one possible solution is to setup two different Gladinet Cloud Enterprise servers, one for company A and one for company B.

However, it may be more efficient if both company A and company B are on the same Gladinet Cloud Enterprise server and each access the file sync and share solution via a different URL. So it is a multi-tenant file sync and share solution with support for multiple different company URLs.

Server Name Indication

The first step is to enable SSL for multiple different URLs because each company would like to access the URL via SSL. To enable multiple HTTPS SSL binding on the same server, first we will need to use Server Name Indication (SNI), which is available in Windows Server 2012. Server Name Indication allows IIS to bind to the same SSL port but with different URL.

The end result is being able to bind to the same SSL port with different Host name.

Enable Multiple Site Binding

Now next step is to enable multiple site binding. This can be done by inspecting the web.config file under the c:\program files (x86)\gladinet cloud enterprise\namespace\web.config file.

Look for the line

<serviceHostingEnvironment aspNetCompatibilityEnabled="true" />

and change it to:

<serviceHostingEnvironment aspNetCompatibilityEnabled="true" multipleSiteBindingsEnabled="true"/>

Disable Gladinet Load Balancing

Because multiple companies are all using the same Gladinet Cloud Enterprise server using different URL, worker-node Load Balancing must be disabled. In the Cluster Control Panel click on Worker Nodes, then click on the Advanced settings:

Then enable the Disable worker-node load balancing setting:

If load balancing is required (in the case of multiple worker nodes), then a third party load balancer must be implemented. 

Now your Gladinet Cloud Enterprise can service multiple companies each on a different company URL.