<?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: TLS 1.3 Qliksense in Management &amp; Governance</title>
    <link>https://community.qlik.com/t5/Management-Governance/TLS-1-3-Qliksense/m-p/2471001#M27666</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/251190"&gt;@mpc&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for the response.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We are running QlikSense on Windows 2022 server - whereas the article you referenced mentions&amp;nbsp;&lt;SPAN&gt;Windows Server 2012, 2016 and 2019 only. Would TLS 1.3 still not work?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;Can you outline what's involved by putting QlikSense beyond a Reverse Proxy?&lt;/P&gt;
&lt;P&gt;Much appreciated&lt;/P&gt;
&lt;P&gt;Dai&lt;/P&gt;</description>
    <pubDate>Tue, 16 Jul 2024 16:38:52 GMT</pubDate>
    <dc:creator>Senor_Dai</dc:creator>
    <dc:date>2024-07-16T16:38:52Z</dc:date>
    <item>
      <title>TLS 1.3 Qliksense</title>
      <link>https://community.qlik.com/t5/Management-Governance/TLS-1-3-Qliksense/m-p/2470980#M27663</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Ive seen from support articles that TLS 1.2 is not yet supported in Qliksense however this is a &lt;A href="https://community.qlik.com/t5/Official-Support-Articles/TLS-and-SSL-Support-in-Qlik-Sense-How-to-configure-Qlik-Sense/ta-p/1713720" target="_self"&gt;workaround outlined&lt;/A&gt;.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;We really need to implement TLS 1.3 as a requirement from our customers.&amp;nbsp; Would amending the registry like achieve this ?&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot 2024-07-16 at 15.56.38.png" style="width: 447px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/169421i4E0D725C7D680FFC/image-dimensions/447x256?v=v2" width="447" height="256" role="button" title="Screenshot 2024-07-16 at 15.56.38.png" alt="Screenshot 2024-07-16 at 15.56.38.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;In the above example Ive added registry keys for TLS 1.0 to 1.3 and 'disabled' all apart from 1.3 which I have enabled.&lt;BR /&gt;&lt;BR /&gt;Will this be detrimental to how QlikSense functions ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Many thanks,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Dai&lt;/P&gt;</description>
      <pubDate>Tue, 16 Jul 2024 15:07:39 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/TLS-1-3-Qliksense/m-p/2470980#M27663</guid>
      <dc:creator>Senor_Dai</dc:creator>
      <dc:date>2024-07-16T15:07:39Z</dc:date>
    </item>
    <item>
      <title>Re: TLS 1.3 Qliksense</title>
      <link>https://community.qlik.com/t5/Management-Governance/TLS-1-3-Qliksense/m-p/2470997#M27665</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Enabling TLS 1.3 will cause errors, as mentioned in this KB:&amp;nbsp;&lt;A href="https://community.qlik.com/t5/Official-Support-Articles/Opening-the-Qlik-Sense-hub-shows-An-error-occurred-Error/ta-p/2427754" target="_blank"&gt;https://community.qlik.com/t5/Official-Support-Articles/Opening-the-Qlik-Sense-hub-shows-An-error-occurred-Error/ta-p/2427754&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Here some informations about differences between TLS 1.2 and 1.3. You can disable weak cipher suits through IIS Crypto recommended settings:&amp;nbsp;&lt;A href="https://www.nartac.com/Products/IISCrypto" target="_blank"&gt;https://www.nartac.com/Products/IISCrypto&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;If access by TLS 1.3 is mandatory, you should put Qlik Sense beyond a Reverse Proxy, which handle the certificate&lt;/P&gt;
&lt;P&gt;Kind regards&lt;/P&gt;</description>
      <pubDate>Tue, 16 Jul 2024 16:22:05 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/TLS-1-3-Qliksense/m-p/2470997#M27665</guid>
      <dc:creator>mpc</dc:creator>
      <dc:date>2024-07-16T16:22:05Z</dc:date>
    </item>
    <item>
      <title>Re: TLS 1.3 Qliksense</title>
      <link>https://community.qlik.com/t5/Management-Governance/TLS-1-3-Qliksense/m-p/2471001#M27666</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/251190"&gt;@mpc&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for the response.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We are running QlikSense on Windows 2022 server - whereas the article you referenced mentions&amp;nbsp;&lt;SPAN&gt;Windows Server 2012, 2016 and 2019 only. Would TLS 1.3 still not work?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;Can you outline what's involved by putting QlikSense beyond a Reverse Proxy?&lt;/P&gt;
&lt;P&gt;Much appreciated&lt;/P&gt;
&lt;P&gt;Dai&lt;/P&gt;</description>
      <pubDate>Tue, 16 Jul 2024 16:38:52 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/TLS-1-3-Qliksense/m-p/2471001#M27666</guid>
      <dc:creator>Senor_Dai</dc:creator>
      <dc:date>2024-07-16T16:38:52Z</dc:date>
    </item>
    <item>
      <title>Re: TLS 1.3 Qliksense</title>
      <link>https://community.qlik.com/t5/Management-Governance/TLS-1-3-Qliksense/m-p/2471087#M27670</link>
      <description>&lt;P&gt;The KB is quite confusing indeed, because it's mention Windows Server 2012 2016 2019 or Qlik Sense all versions:&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Neither the listed versions of Windows, &lt;STRONG&gt;nor&lt;/STRONG&gt; Qlik Sense Enterprise on Windows support TLS 1.3. See&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://community.qlik.com/t5/Official-Support-Articles/Supported-TLS-and-SSL-Protocols-and-Ciphers/ta-p/1710345#:~:text=TLS%201.3/2.0%20are%20not%20yet%20fully%20supported%20%5BInternal%20Reference%20ID%3A%C2%A0SHEND%2D1269%5D" target="_blank" rel="noopener"&gt;Supported TLS and SSL Protocols and Ciphers&lt;/A&gt;&lt;SPAN&gt;.&lt;BR /&gt;In the link above:&amp;nbsp;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H3 id="toc-hId-1254250992"&gt;&lt;FONT color="#339966"&gt;&lt;SPAN&gt;&lt;STRONG&gt;Qlik Sense Enterprise on Windows:&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;UL&gt;
&lt;LI&gt;Full Support for&lt;FONT color="#339966"&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;TLS 1.2&lt;/STRONG&gt;&lt;/FONT&gt;&amp;nbsp;from version June 2017&amp;nbsp;&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;TLS 1.3/2.0 are not yet fully supported&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/STRONG&gt;[Internal Reference ID:&amp;nbsp;SHEND-1269]&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;By putting Qlik Sense behind a Reverse Proxy, you'll be able to use for 1.2 TLS for Qlik Sense services communications, and through the Reverse Proxy, use a 1.3 TLS certificates, to communicate from user browser to Qlik Sense Proxy.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Please find the schema bellow:&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="mpc_0-1721199086656.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/169454i2C89E9D6E58505D2/image-size/medium?v=v2&amp;amp;px=400" role="button" title="mpc_0-1721199086656.png" alt="mpc_0-1721199086656.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;It this more clear ?&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Kind regards&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 17 Jul 2024 06:52:03 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/TLS-1-3-Qliksense/m-p/2471087#M27670</guid>
      <dc:creator>mpc</dc:creator>
      <dc:date>2024-07-17T06:52:03Z</dc:date>
    </item>
  </channel>
</rss>

