Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
vindhya_giri
Creator II
Creator II

QlikView and IIS for SSL configuration

Hello,

I have read quite a few posts and blogs but did not get a clear understanding of the solution.

Using QlikView 11.2 SR10

Using IIS 7 as WebServer

Attached is the document followed for the implementation.

Steps followed:

1. SSL certificate created

2. Followed steps in Chapter 3.1 and 3.2 from the attached doc.

3. Followed the steps in Chapter 5  from the attached doc.

Results:

QlikView Management  console and Access Point working as expected without any issues.

Issues:

1. The updated URL for QlikView Distribution Service in QMC is not opening the corresponding XML file.

2. The updated URL for QlikView Directory Service Connector in QMC is not opening the corresponding XML file.

3. The updated URL for QlikView Web Servers in QMC is not opening the corresponding XML file.

When trying to open the updated URL, getting the following error:


This page can't be displayed". Turn on TLS 1.0, TLS 1.1, and TLS 1.2 in Advanced settings and try connecting to 'updated URL' again. If this error persists, it is possible that this site uses an unsupported protocol or cipher suite such as RC4 (link for the details), which is not considered secure. Please contact your site administrator.


When looked into the Internet Properties advanced: Use TLS 1.0, 1.1, 1.2 are tick marked


The attached document said to check if all the services are connected and running (and in my case all the services are connected and running) but did not mention if any error occurred when trying to open the URL.Was not sure if anyone else came across the same scenario. Looking forward for suggestions to resolve the issue.


Thanks 


Regard

Vindhya


Labels (1)
6 Replies
Not applicable

Vindhya,


Don't mean to take this post in a different direction but were you able to connect to QMC over port 443 using IIS?


We have the following configuration and can connect to access point but not QlikView Management  Console:


Windoiws Server 2012 R2

IIS8

Qlikview Server 11.2 SR14


The document you've attached has slightly different versions and shows how to configure QMC for SSL using Qlikview Webserver but not IIS.


Thanks,

Marc

vindhya_giri
Creator II
Creator II
Author

Hi Marc,

Chapter 5 of the document has the steps to make QMC use https URL rather than http.

Chapter 5, Point # 25: https://<FullyQualifiedServerDomainName>:4780/qmc/default.htm

This is the URL I am able to use. It is still using port 4780 but we have registered all the ports to use https for SSL encrypted communication.

You have AccessPoint URL as https and QMC as http?

Are you using URL rewrite or followed any other steps different from the document attached in the original post?

Thanks

Regards

Vindhya

Not applicable

Hi Vindhya,

Our configuration requires everything on one server (IIS, Qlikview Server, etc) and all communication to the outside internet use port 443. With Qlikview Access Point already listening on 443 we need a way for QMC to communicate on that port as well. Investigating using multiple IP address and other options with Qlik support.

Can you think of a way to do this? We can't find any documentation.

freinholdson
Partner - Contributor III
Partner - Contributor III

Hi Vindhya,


Did you manage to solve this? I have the exact same problem. Everything is set up per instructions but the XML-links in the QMC gives the TLS error and the services actually still seems to run http even though everything is set up to use https.


Browsing to https://machinename:4730/DSC/Service gives the TLS error. Browsing to http (http://machinename:4730/DSC/Service) still works as well and I guess that should not work when everything is set up to use https.


Thanks!


vindhya_giri
Creator II
Creator II
Author

Hi Filip,

I could not find a solution for it. I have left those 3 URL's as http in QMC (QlikView Distribution Service , QlikView Directory Service Connector, QlikView Web Servers)

Thanks

Regards

Vindhya

freinholdson
Partner - Contributor III
Partner - Contributor III

Ok, I gave up trying to solve it that way and reinstalled QlikView on the servers with certificate trust mode instead of Windows authorization. Now the services are up and running and authorized through QlikView's own certificates.