<?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 HTTPS -secure connection in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/HTTPS-secure-connection/m-p/660896#M1065353</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello QV geniuses,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do I need a 3rd party SSL certificate to use "https" when accessing QV documents?Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 22 Sep 2014 11:03:26 GMT</pubDate>
    <dc:creator />
    <dc:date>2014-09-22T11:03:26Z</dc:date>
    <item>
      <title>HTTPS -secure connection</title>
      <link>https://community.qlik.com/t5/QlikView/HTTPS-secure-connection/m-p/660896#M1065353</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello QV geniuses,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do I need a 3rd party SSL certificate to use "https" when accessing QV documents?Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Sep 2014 11:03:26 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/HTTPS-secure-connection/m-p/660896#M1065353</guid>
      <dc:creator />
      <dc:date>2014-09-22T11:03:26Z</dc:date>
    </item>
    <item>
      <title>Re: HTTPS -secure connection</title>
      <link>https://community.qlik.com/t5/QlikView/HTTPS-secure-connection/m-p/660897#M1065354</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, Reagan&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; You can use any kind of SSL certificate. Of course if the certificate is not generated by a CA, que the customers connect to the QlikView WebServer a security issue is going to be shown on their browser. When using a third party certificate, this 3rd party "authenticates" that the certificate in use is legitimate.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Beyond that, it works with an self signed certificate as well.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Nov 2014 11:36:54 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/HTTPS-secure-connection/m-p/660897#M1065354</guid>
      <dc:creator>Luis_Cortizo</dc:creator>
      <dc:date>2014-11-27T11:36:54Z</dc:date>
    </item>
  </channel>
</rss>

