Configure Sisense for multiple domains

We would like to configure our Azure application gateway to allow access to Sisense under 2 totally different domains. One is a legacy domain and one is our new domain.

I raised a ticket with Sisense support. Sisense itself cannot by configured. they suggested setting up routing in our load balancer / DNS to do this. So I did this, but Azure Application gateway throws an error. The problem is the SSL certificate installed in Sisense is for the old domain. anybody got round this . perhaps a forwardiing instead of a redirect?

chriskerrison21

Posted 1 year ago·Last reply 1 year ago

4 comments

Andrii Lohvin

·1 year ago

Hi chriskerrison21

First of all, you should avoid changing any settings in IIS. IIS hosts an internal Sisense component rather than a web application, and must remain with the default settings. Any changes to IIS will likely result in application inaccessibility.

Regarding your task, I see three options:

Redirect users from the old DNS to a new one instead of assigning both to the same server. This is a common practice - you can host a simple redirection web server on another machine that will redirect users to a new one. This option does not require complex configurations, and you can shut down the redirection server once all users have become accustomed to the new DNS.
Create a multi-domain SSL certificate and use it to configure SSL in Sisense on the application level. With the multi-domain certificate in place, you can simply assign another DNS name to the same server via CNAME. The SSL configuration in Sisense is done via http://localhost:3030 on the Sisense server. Details: https://docs.sisense.com/win/SisenseWin/setting-up-ssl-for-sisense-windows.htm.
Configure SSL termination on the Azure side and reconfigure the Sisense application to listen on HTTP. Moving Sisense from SSL to HTTP is also done on the http://localhost:3030 page. At first glance, it appears possible to configure two certificates on the Azure side via Application Gateway (https://learn.microsoft.com/en-us/azure/application-gateway/multiple-site-overviewhttps://learn.microsoft.com/en-us/azure/application-gateway/multiple-site-overview), but you may want to double-check with the Azure support team on the best approach to achieve this task.

Please note that on the Sisense application side, there is an Alias parameter configured on the Admin page. This parameter controls the hyperlinks to Sisense assets in Sisense-generated emails. You will have to set the Alias to one of the domains, as it does not allow multiple entries.

Oleg Valynkin

·1 year ago

I assume you have a nginx-ingress installed on the Sisense instance but it should be just a generic HTTP in this case with the default 30845 port

chriskerrison21

OP1 year ago

Hello, I've no idea if we have nginix-ingress install. We have an old Windows version of Sisense v8.1, so this doesn't run in IIS. But I see there is some SisenseWeb site set up in IIS, but this doens't render so much be old.

So can you expand on what you meant please?

thanks

DRay

·1 year ago

Hello chriskerrison21,

Thank you for reaching out. I see your question hasn't gotten a response yet, so I'm asking internally to try and get you an answer.