<?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 Logging in to QlikSense session with enigma.js and prefixed virtual proxy in Integration, Extension &amp; APIs</title>
    <link>https://community.qlik.com/t5/Integration-Extension-APIs/Logging-in-to-QlikSense-session-with-enigma-js-and-prefixed/m-p/1564255#M10274</link>
    <description>&lt;P&gt;Hi Qlik Experts&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am building a client side application with vue.js and connecting to QS with enigma.js&lt;/P&gt;&lt;P&gt;I authenticate with session&amp;nbsp;notification:OnAuthenticationInformation handler by redirecting to loginUri and then back to my app.&lt;/P&gt;&lt;P&gt;If I use default QS virtual proxy, everything works as a charm. But if I use custom QS virtual proxy with a prefix, I get my mustAuthenticate = true all the time and no cookie is being created for QS server domain.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If I use QS hub to log in to this prefixed virtual proxy, cookie is created and I can login just fine.&lt;/P&gt;&lt;P&gt;Could someone advice, why is it happening and how to fix it&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Darius&lt;/P&gt;</description>
    <pubDate>Wed, 03 Apr 2019 04:26:11 GMT</pubDate>
    <dc:creator>d_pranskus</dc:creator>
    <dc:date>2019-04-03T04:26:11Z</dc:date>
    <item>
      <title>Logging in to QlikSense session with enigma.js and prefixed virtual proxy</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/Logging-in-to-QlikSense-session-with-enigma-js-and-prefixed/m-p/1564255#M10274</link>
      <description>&lt;P&gt;Hi Qlik Experts&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am building a client side application with vue.js and connecting to QS with enigma.js&lt;/P&gt;&lt;P&gt;I authenticate with session&amp;nbsp;notification:OnAuthenticationInformation handler by redirecting to loginUri and then back to my app.&lt;/P&gt;&lt;P&gt;If I use default QS virtual proxy, everything works as a charm. But if I use custom QS virtual proxy with a prefix, I get my mustAuthenticate = true all the time and no cookie is being created for QS server domain.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If I use QS hub to log in to this prefixed virtual proxy, cookie is created and I can login just fine.&lt;/P&gt;&lt;P&gt;Could someone advice, why is it happening and how to fix it&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Darius&lt;/P&gt;</description>
      <pubDate>Wed, 03 Apr 2019 04:26:11 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/Logging-in-to-QlikSense-session-with-enigma-js-and-prefixed/m-p/1564255#M10274</guid>
      <dc:creator>d_pranskus</dc:creator>
      <dc:date>2019-04-03T04:26:11Z</dc:date>
    </item>
    <item>
      <title>Re: Logging in to QlikSense session with enigma.js and prefixed virtual proxy</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/Logging-in-to-QlikSense-session-with-enigma-js-and-prefixed/m-p/1570889#M10361</link>
      <description>&lt;P&gt;&lt;SPAN&gt;hello,&lt;/SPAN&gt;&lt;BR /&gt;&lt;A href="https://github.com/qlik-oss/enigma.js/tree/master/examples/authentication/sense-using-jwt" target="_blank" rel="nofollow noopener noreferrer"&gt;https://github.com/qlik-oss/enigma.js/tree/master/examples/authentication/sense-using-jwt&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;thanks &amp;amp; regard&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Harsh Gohil&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 18 Apr 2019 09:18:22 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/Logging-in-to-QlikSense-session-with-enigma-js-and-prefixed/m-p/1570889#M10361</guid>
      <dc:creator>iharsh220</dc:creator>
      <dc:date>2019-04-18T09:18:22Z</dc:date>
    </item>
  </channel>
</rss>

