Qlik Sense - Chainging default virtual proxy.

[csellei]

Hi,

Is It possible to change the default virtual proxy in Sense?

Best regards.

Christian

[korsikov]

hello Christian.

What you want to do?

[csellei]

Hi Alexander,

I deployed a virtual proxy with a custom atuthentication module. Customer wants to redirect qliksense.company.com.ar to https://IP. If they use https://IP, it redicts to default virtual proxy (http://IP/Hub). What they need is to redirect as default to https://IP/Web/Hub (Web is the alternative virtual proxy).

AS far as I know, "Is virtual proxy" check box can't be disable at the default virtual proxy, and is not present at the alternative virtual proxy. That's why I'm thinking is not posible to change.

May be they can use qliksense.company.com.ar/Web, but main idea is that user use inly qliksense.company.com.ar.

Best regards.

[korsikov]

i'm see two way's solve this problem

1. Change Default proxy auth module

2. or user nginx as frontend proxy. my example here  https://community.qlik.com/message/1096955#1096955

[mountaindude]

I have been struggling with this too.

Does not seem to be possible to change the default virtual proxy (VP) to a VP that you have defined yourself.

And the default VP is locked to be Ticket based, e.g. cannot be changed to header or SAML based (which means that option 1 above will not work)

There's got to be a way around this...

Using Sense 3.0.1 btw.

[Anonymous]

Hi Christian,

I had the same issue but found a work around.

1. Install and configure IIS on Qlik Sense server - This should then give you the IIS Start Page when attempting to access http://IP

2. Find the iisstart.htm file in C:\inetpub\wwwroot

3. Open the file and paste the following Javascript after the line <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />

<script type="text/javascript">

            window.location.href = "https://IP/WEB/"

        </script>

4. Save the File (you need elevated admin privileges).

Now when users visit http://IP the javascript will redirect to your virtual proxy.

[mountaindude]

Ahh yes - nice and clean solution.

Only downside is you need IIS to be running on the server, but that's ok I guess (as long as it's locked down properly and don't expose any security holes).

I found another solution too, btw.

If you change the default virtual proxy so that

a. it has a prefix (e.g. winauth), and

b. it has a unique cookie header name (e.g. X-Qlik-Session-winauth)

this will free up the https://<FQDN>/ endpoint. Now remove the prefix from your SAML or whatever other virtual proxy you want to be at the root, and voila - https://<FQDN>/ now uses the auth mechanism of your choice.

You can still use https://<FQDN>/winauth when needed.

In combination with Gareth_Wilson‌'s suggestion for http to https redirection, you get a lot of flexibility.

Setting up a reverse proxy in front of the whole Sense environment still provides best flexibility, but also requires a lot more work/skills.