<?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: Qlik sense virtual proxy not working after upgrading Qlik sense 2018 to 2023 in Integration, Extension &amp; APIs</title>
    <link>https://community.qlik.com/t5/Integration-Extension-APIs/Qlik-sense-virtual-proxy-not-working-after-upgrading-Qlik-sense/m-p/2110820#M19090</link>
    <description>&lt;P&gt;yes, I am able to open my application with the same vp from the hub&lt;/P&gt;
&lt;P&gt;my licensing model is&amp;nbsp;&lt;SPAN&gt;Capacity-based&amp;nbsp;i believe and like i said earlier vp was working perfectly fine before i update the version of qlik..&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot 2023-08-29 at 14.38.34.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/115297iDB75708539174D9B/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Screenshot 2023-08-29 at 14.38.34.png" alt="Screenshot 2023-08-29 at 14.38.34.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt; &lt;/P&gt;</description>
    <pubDate>Tue, 29 Aug 2023 11:39:57 GMT</pubDate>
    <dc:creator>gmuradov</dc:creator>
    <dc:date>2023-08-29T11:39:57Z</dc:date>
    <item>
      <title>Qlik sense virtual proxy not working after upgrading Qlik sense 2018 to 2023</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/Qlik-sense-virtual-proxy-not-working-after-upgrading-Qlik-sense/m-p/2110453#M19082</link>
      <description>&lt;P&gt;Hello guys,&lt;/P&gt;
&lt;P&gt;After upgrading qlik sense version from 2018 to august 2023 my virtual proxy stopped working.&lt;/P&gt;
&lt;P&gt;I am using the virtual proxy as a src in iframe in order to be able to show the dashboards in my html files.&lt;/P&gt;
&lt;P&gt;See below the settings on the proxy and the error i get in the console.&lt;/P&gt;
&lt;P&gt;Before the update of the version everything was working ok.&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;
&lt;P&gt;PS: i also tried with new virtual proxy but i get the same error &lt;span class="lia-unicode-emoji" title=":confused_face:"&gt;😕&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 28 Aug 2023 18:47:23 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/Qlik-sense-virtual-proxy-not-working-after-upgrading-Qlik-sense/m-p/2110453#M19082</guid>
      <dc:creator>gmuradov</dc:creator>
      <dc:date>2023-08-28T18:47:23Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik sense virtual proxy not working after upgrading Qlik sense 2018 to 2023</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/Qlik-sense-virtual-proxy-not-working-after-upgrading-Qlik-sense/m-p/2110539#M19083</link>
      <description>&lt;P&gt;Hi, check your entries on host whitelist.&lt;/P&gt;
&lt;P&gt;Rules for those addresses have changed. No "*" may be used.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.qlik.com/t5/Official-Support-Articles/How-to-configure-the-WebSocket-origin-allow-list-and-best/ta-p/1716765" target="_blank"&gt;https://community.qlik.com/t5/Official-Support-Articles/How-to-configure-the-WebSocket-origin-allow-list-and-best/ta-p/1716765&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 28 Aug 2023 18:22:56 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/Qlik-sense-virtual-proxy-not-working-after-upgrading-Qlik-sense/m-p/2110539#M19083</guid>
      <dc:creator>annapochyla</dc:creator>
      <dc:date>2023-08-28T18:22:56Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik sense virtual proxy not working after upgrading Qlik sense 2018 to 2023</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/Qlik-sense-virtual-proxy-not-working-after-upgrading-Qlik-sense/m-p/2110542#M19084</link>
      <description>&lt;P&gt;Hi, thanks for the suggestion but the host whitelist is configured correctly &lt;span class="lia-unicode-emoji" title=":confused_face:"&gt;😕&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 28 Aug 2023 18:33:48 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/Qlik-sense-virtual-proxy-not-working-after-upgrading-Qlik-sense/m-p/2110542#M19084</guid>
      <dc:creator>gmuradov</dc:creator>
      <dc:date>2023-08-28T18:33:48Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik sense virtual proxy not working after upgrading Qlik sense 2018 to 2023</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/Qlik-sense-virtual-proxy-not-working-after-upgrading-Qlik-sense/m-p/2110544#M19085</link>
      <description>&lt;P&gt;What about the SameSite attributes?&lt;/P&gt;
&lt;P&gt;Try and set the to "None" (the most permissive) to test.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Had similar issue with iframes in the past when the browsers started "demanding" the session cookie to have SameSite attribute set. &lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="stefanstoichev123_0-1693247933684.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/115255i6DB435EE2CBE0589/image-size/medium?v=v2&amp;amp;px=400" role="button" title="stefanstoichev123_0-1693247933684.png" alt="stefanstoichev123_0-1693247933684.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards!&lt;/P&gt;
&lt;P&gt;Stefan&lt;/P&gt;</description>
      <pubDate>Mon, 28 Aug 2023 18:40:33 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/Qlik-sense-virtual-proxy-not-working-after-upgrading-Qlik-sense/m-p/2110544#M19085</guid>
      <dc:creator>stefanstoichev123</dc:creator>
      <dc:date>2023-08-28T18:40:33Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik sense virtual proxy not working after upgrading Qlik sense 2018 to 2023</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/Qlik-sense-virtual-proxy-not-working-after-upgrading-Qlik-sense/m-p/2110545#M19086</link>
      <description>&lt;P&gt;just tried but i keep getting the same error &lt;span class="lia-unicode-emoji" title=":confused_face:"&gt;😕&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 28 Aug 2023 18:45:32 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/Qlik-sense-virtual-proxy-not-working-after-upgrading-Qlik-sense/m-p/2110545#M19086</guid>
      <dc:creator>gmuradov</dc:creator>
      <dc:date>2023-08-28T18:45:32Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik sense virtual proxy not working after upgrading Qlik sense 2018 to 2023</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/Qlik-sense-virtual-proxy-not-working-after-upgrading-Qlik-sense/m-p/2110678#M19088</link>
      <description>&lt;P&gt;Can you confirm that you are able to open your application, using the same unauthenticated VP, also from the Hub?&lt;BR /&gt;Also take a look at your licensing model:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;SPAN&gt;User-based licenses, with professional access and analyzer access, do not support anonymous authentication. Capacity-based licenses will allow anonymous authentication using an Analyzer Capacity license (signed key) or a Token license.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;For the anonymous authentication method to be operational, you need to create a license rule that allows anonymous users for either an Analyzer Capacity license (requires a signed license key) or a Login Access Token&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN&gt;as reported here:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://help.qlik.com/en-US/sense-admin/May2023/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Administer_QSEoW/Managing_QSEoW/anonymous-authentication.htm" target="_blank" rel="noopener"&gt;https://help.qlik.com/en-US/sense-admin/May2023/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Administer_QSEoW/Managing_QSEoW/anonymous-authentication.htm&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 29 Aug 2023 06:57:35 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/Qlik-sense-virtual-proxy-not-working-after-upgrading-Qlik-sense/m-p/2110678#M19088</guid>
      <dc:creator>Giovanni_Civardi</dc:creator>
      <dc:date>2023-08-29T06:57:35Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik sense virtual proxy not working after upgrading Qlik sense 2018 to 2023</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/Qlik-sense-virtual-proxy-not-working-after-upgrading-Qlik-sense/m-p/2110820#M19090</link>
      <description>&lt;P&gt;yes, I am able to open my application with the same vp from the hub&lt;/P&gt;
&lt;P&gt;my licensing model is&amp;nbsp;&lt;SPAN&gt;Capacity-based&amp;nbsp;i believe and like i said earlier vp was working perfectly fine before i update the version of qlik..&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot 2023-08-29 at 14.38.34.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/115297iDB75708539174D9B/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Screenshot 2023-08-29 at 14.38.34.png" alt="Screenshot 2023-08-29 at 14.38.34.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt; &lt;/P&gt;</description>
      <pubDate>Tue, 29 Aug 2023 11:39:57 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/Qlik-sense-virtual-proxy-not-working-after-upgrading-Qlik-sense/m-p/2110820#M19090</guid>
      <dc:creator>gmuradov</dc:creator>
      <dc:date>2023-08-29T11:39:57Z</dc:date>
    </item>
  </channel>
</rss>

