<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Multiple SSL certificates for multiple domain name access in Management &amp; Governance</title>
    <link>https://community.qlik.com/t5/Management-Governance/Multiple-SSL-certificates-for-multiple-domain-name-access/m-p/1733178#M16480</link>
    <description>&lt;P&gt;We would like to setup two SSL certificates for multiple domain name access for one Qlik Sense server.&lt;/P&gt;&lt;P data-unlink="true"&gt;&lt;BR /&gt;We have one Qlik Sense Server installed in our local domain: &lt;A href="https://qlik01.ourdomain.local" target="_blank"&gt;https://qlik01.ourdomain.local&lt;/A&gt; &amp;nbsp;&lt;BR /&gt;The server is using a self signed certificate.&lt;BR /&gt;I would like to give external companies access to our qlik sense server using &lt;A href="https://qlik.ourcompany.com" target="_blank"&gt;https://qlik.ourcompany.com&lt;/A&gt;&lt;BR /&gt;I have a valid wildcart SSL certificate for *.ourcompany.com.&lt;/P&gt;&lt;P data-unlink="true"&gt;&lt;BR /&gt;I tried setting up a new node with the proxy service enabled, for host name qlik.ourcompany.com.&lt;BR /&gt;Then I added the thumbprint of the imported wildcart certificate for *.ourcompany.com to the proxy for the new node.&lt;BR /&gt;When accessing Qlik Sense from an external address using qlik.ourcompany.com, I still get a warning because it's using the self-signed certificate for qlik01.ourdomain.local instead of the wildcard certificate.&lt;/P&gt;&lt;P data-unlink="true"&gt;&lt;BR /&gt;How can I set this up properly?&lt;/P&gt;</description>
    <pubDate>Sat, 16 Nov 2024 01:44:35 GMT</pubDate>
    <dc:creator>nivdv</dc:creator>
    <dc:date>2024-11-16T01:44:35Z</dc:date>
    <item>
      <title>Multiple SSL certificates for multiple domain name access</title>
      <link>https://community.qlik.com/t5/Management-Governance/Multiple-SSL-certificates-for-multiple-domain-name-access/m-p/1733178#M16480</link>
      <description>&lt;P&gt;We would like to setup two SSL certificates for multiple domain name access for one Qlik Sense server.&lt;/P&gt;&lt;P data-unlink="true"&gt;&lt;BR /&gt;We have one Qlik Sense Server installed in our local domain: &lt;A href="https://qlik01.ourdomain.local" target="_blank"&gt;https://qlik01.ourdomain.local&lt;/A&gt; &amp;nbsp;&lt;BR /&gt;The server is using a self signed certificate.&lt;BR /&gt;I would like to give external companies access to our qlik sense server using &lt;A href="https://qlik.ourcompany.com" target="_blank"&gt;https://qlik.ourcompany.com&lt;/A&gt;&lt;BR /&gt;I have a valid wildcart SSL certificate for *.ourcompany.com.&lt;/P&gt;&lt;P data-unlink="true"&gt;&lt;BR /&gt;I tried setting up a new node with the proxy service enabled, for host name qlik.ourcompany.com.&lt;BR /&gt;Then I added the thumbprint of the imported wildcart certificate for *.ourcompany.com to the proxy for the new node.&lt;BR /&gt;When accessing Qlik Sense from an external address using qlik.ourcompany.com, I still get a warning because it's using the self-signed certificate for qlik01.ourdomain.local instead of the wildcard certificate.&lt;/P&gt;&lt;P data-unlink="true"&gt;&lt;BR /&gt;How can I set this up properly?&lt;/P&gt;</description>
      <pubDate>Sat, 16 Nov 2024 01:44:35 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Multiple-SSL-certificates-for-multiple-domain-name-access/m-p/1733178#M16480</guid>
      <dc:creator>nivdv</dc:creator>
      <dc:date>2024-11-16T01:44:35Z</dc:date>
    </item>
  </channel>
</rss>

