<?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 Re: SSL for NPrinting Sep 2018 in Qlik NPrinting</title>
    <link>https://community.qlik.com/t5/Qlik-NPrinting/SSL-for-NPrinting-Sep-2018/m-p/1523917#M21829</link>
    <description>&lt;P&gt;I don't see why not. A valid wildcard&amp;nbsp;ssl certificate is just a valid ssl certificate. Have you tried it?&lt;/P&gt;</description>
    <pubDate>Wed, 26 Dec 2018 07:15:22 GMT</pubDate>
    <dc:creator>Gysbert_Wassenaar</dc:creator>
    <dc:date>2018-12-26T07:15:22Z</dc:date>
    <item>
      <title>SSL for NPrinting Sep 2018</title>
      <link>https://community.qlik.com/t5/Qlik-NPrinting/SSL-for-NPrinting-Sep-2018/m-p/1523885#M21826</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;I'm trying to implement SSL cert on NPrinting following instructions in&amp;nbsp;&amp;nbsp;&lt;A href="https://help.qlik.com/en-US/nprinting/September2018/Content/NPrinting/DeployingQVNprinting/Installing-ssl-certificates.htm" target="_blank"&gt;https://help.qlik.com/en-US/nprinting/September2018/Content/NPrinting/DeployingQVNprinting/Installing-ssl-certificates.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Can the CN in the SSL certificate purchased from CA contain wildcard?&lt;/P&gt;&lt;P&gt;Many Thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 26 Dec 2018 02:43:44 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-NPrinting/SSL-for-NPrinting-Sep-2018/m-p/1523885#M21826</guid>
      <dc:creator>socialgeekqv</dc:creator>
      <dc:date>2018-12-26T02:43:44Z</dc:date>
    </item>
    <item>
      <title>Re: SSL for NPrinting Sep 2018</title>
      <link>https://community.qlik.com/t5/Qlik-NPrinting/SSL-for-NPrinting-Sep-2018/m-p/1523917#M21829</link>
      <description>&lt;P&gt;I don't see why not. A valid wildcard&amp;nbsp;ssl certificate is just a valid ssl certificate. Have you tried it?&lt;/P&gt;</description>
      <pubDate>Wed, 26 Dec 2018 07:15:22 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-NPrinting/SSL-for-NPrinting-Sep-2018/m-p/1523917#M21829</guid>
      <dc:creator>Gysbert_Wassenaar</dc:creator>
      <dc:date>2018-12-26T07:15:22Z</dc:date>
    </item>
    <item>
      <title>Re: SSL for NPrinting Sep 2018</title>
      <link>https://community.qlik.com/t5/Qlik-NPrinting/SSL-for-NPrinting-Sep-2018/m-p/1523924#M21831</link>
      <description>&lt;P&gt;I did, couldn't get it to work. According to Qlik help:&lt;/P&gt;&lt;P&gt;&lt;A href="https://help.qlik.com/en-US/nprinting/September2018/Content/NPrinting/DeployingQVNprinting/Managing-cert.htm" target="_blank"&gt;https://help.qlik.com/en-US/nprinting/September2018/Content/NPrinting/DeployingQVNprinting/Managing-cert.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;"&lt;SPAN&gt;An important field is the Common Name (CN), which should be the exact Fully Qualified Domain Name (FQDN) of the host that you intend to use the certificate with. For example, if the URL of your&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="CommonComponentsNewsStand"&gt;NewsStand&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;is &lt;A href="https://yourcompany.com:4994" target="_blank"&gt;https://yourcompany.com:4994&lt;/A&gt; the FQND is yourcompany.com (the port is not part of the FQDN). If the URL of your&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="CommonComponentsNewsStand"&gt;NewsStand&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;is &lt;A href="https://www.yourcompany.com:4994" target="_blank"&gt;https://www.yourcompany.com:4994&lt;/A&gt; the FQND is &lt;A href="http://www.yourcompany.com" target="_blank"&gt;www.yourcompany.com&lt;/A&gt; and it is different from yourcompany.com so, if you want to use both, you must use two certificates."&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Can I generate the private key from the cert provided by CA?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 26 Dec 2018 07:48:02 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-NPrinting/SSL-for-NPrinting-Sep-2018/m-p/1523924#M21831</guid>
      <dc:creator>socialgeekqv</dc:creator>
      <dc:date>2018-12-26T07:48:02Z</dc:date>
    </item>
    <item>
      <title>Re: SSL for NPrinting Sep 2018</title>
      <link>https://community.qlik.com/t5/Qlik-NPrinting/SSL-for-NPrinting-Sep-2018/m-p/1524088#M21837</link>
      <description>&lt;P&gt;Too bad. NPrinting has some quirks that could have been designed better. Guess this is one of them. You'll need another certificate that's not a wildcard certificate. The CA never had your private key so it's also not in the certificate your CA provided. That key should be on the system where you generated the private key and the csr for the certificate.&lt;/P&gt;</description>
      <pubDate>Wed, 26 Dec 2018 14:43:31 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-NPrinting/SSL-for-NPrinting-Sep-2018/m-p/1524088#M21837</guid>
      <dc:creator>Gysbert_Wassenaar</dc:creator>
      <dc:date>2018-12-26T14:43:31Z</dc:date>
    </item>
  </channel>
</rss>

