Skip to main content
Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE
cancel
Showing results for 
Search instead for 
Did you mean: 
avastani
Partner - Creator III
Partner - Creator III

SSL for EC2 instance with Qlik Web Connector

Hi,

has anyone managed to run an AWS instance of Qlik Web Connector over SSL? Would welcome any help.

I have managed to run and bind my connector over SSL but it only works if I am within the EC2 instance, as the certificate is based on Computer Name whereas my AWS instance uses Elastic IP for access externally.

I am using the same certificate that is created by QlikSense installation and skipping the makecert and pvk2pfx steps.

Here's a reference to running the connector over SSL from the old QVSource days

Running Over SSL - QVSource: The QlikView & Qlik Sense API Connector (Docs)

1 Solution

Accepted Solutions
avastani
Partner - Creator III
Partner - Creator III
Author

Never mind, I solved my own problem, enabled the inbound security group rule to enable 5556 for traffic.

would be great to have a list of outbound rules to be enabled for EC2 instance

Steps followed

1. Bind SSL Certificate;

  1. Check that certificate is not bound already
    1. netsh http show sslcert ipport=0.0.0.0:5556
    2. bind the certificate - netsh http add sslcert ipport=0.0.0.0:5556 certhash=‎(your certificate thumbprint from Certificates snap in in MMC) appid={004FC337-C805-4623-8E5B-B2FCE18F0719}
      1. The Guid above i did not change
    3. netsh http show sslcert ipport=0.0.0.0:5556 to confirm the certificate is bound

Test on the AWS EC2 instance locally using https://machinename:5556/web

I used Elastic IP for my case and for external machine used http://el.as.tic.ip:5556/web and it worked just like the documentation mentions. Based on browser you can Store the Exception permanently or handle based on your browser design and personal preferences

View solution in original post

1 Reply
avastani
Partner - Creator III
Partner - Creator III
Author

Never mind, I solved my own problem, enabled the inbound security group rule to enable 5556 for traffic.

would be great to have a list of outbound rules to be enabled for EC2 instance

Steps followed

1. Bind SSL Certificate;

  1. Check that certificate is not bound already
    1. netsh http show sslcert ipport=0.0.0.0:5556
    2. bind the certificate - netsh http add sslcert ipport=0.0.0.0:5556 certhash=‎(your certificate thumbprint from Certificates snap in in MMC) appid={004FC337-C805-4623-8E5B-B2FCE18F0719}
      1. The Guid above i did not change
    3. netsh http show sslcert ipport=0.0.0.0:5556 to confirm the certificate is bound

Test on the AWS EC2 instance locally using https://machinename:5556/web

I used Elastic IP for my case and for external machine used http://el.as.tic.ip:5556/web and it worked just like the documentation mentions. Based on browser you can Store the Exception permanently or handle based on your browser design and personal preferences