<?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 header based authentication for health check API in Scalability</title>
    <link>https://community.qlik.com/t5/Scalability/Qlik-Sense-header-based-authentication-for-health-check-API/m-p/1549531#M1574</link>
    <description>&lt;P&gt;Sure. The QPS exposed path (&lt;A href="https://foo.company.com{/prefix}/engine/healthcheck" target="_blank"&gt;https://foo.company.com{/prefix}/engine/healthcheck&lt;/A&gt;) should honor any authentication setup on the virtual proxies. Is this not working?&lt;/P&gt;</description>
    <pubDate>Wed, 27 Feb 2019 01:34:32 GMT</pubDate>
    <dc:creator>Levi_Turner</dc:creator>
    <dc:date>2019-02-27T01:34:32Z</dc:date>
    <item>
      <title>Qlik Sense header based authentication for health check API</title>
      <link>https://community.qlik.com/t5/Scalability/Qlik-Sense-header-based-authentication-for-health-check-API/m-p/1549407#M1573</link>
      <description>&lt;P&gt;Hello All, Is it possible to implement header based authentication for Qlik Sense health check APIs?&lt;/P&gt;&lt;P&gt;Currently in our environment, only kerberos authentication is enabled and its complicates the development of an automated tool which can periodically gets data from this API and dumps to a time series database for analysis.&amp;nbsp;&lt;/P&gt;&lt;P&gt;The enterprise QS URL looks like :&amp;nbsp;&lt;/P&gt;&lt;P&gt;https://&amp;lt;servername&amp;gt;/engine/healthcheck/&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Ganesh&lt;/P&gt;</description>
      <pubDate>Tue, 26 Feb 2019 18:28:48 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Scalability/Qlik-Sense-header-based-authentication-for-health-check-API/m-p/1549407#M1573</guid>
      <dc:creator>ganeshkale</dc:creator>
      <dc:date>2019-02-26T18:28:48Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Sense header based authentication for health check API</title>
      <link>https://community.qlik.com/t5/Scalability/Qlik-Sense-header-based-authentication-for-health-check-API/m-p/1549531#M1574</link>
      <description>&lt;P&gt;Sure. The QPS exposed path (&lt;A href="https://foo.company.com{/prefix}/engine/healthcheck" target="_blank"&gt;https://foo.company.com{/prefix}/engine/healthcheck&lt;/A&gt;) should honor any authentication setup on the virtual proxies. Is this not working?&lt;/P&gt;</description>
      <pubDate>Wed, 27 Feb 2019 01:34:32 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Scalability/Qlik-Sense-header-based-authentication-for-health-check-API/m-p/1549531#M1574</guid>
      <dc:creator>Levi_Turner</dc:creator>
      <dc:date>2019-02-27T01:34:32Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Sense header based authentication for health check API</title>
      <link>https://community.qlik.com/t5/Scalability/Qlik-Sense-header-based-authentication-for-health-check-API/m-p/1551220#M1576</link>
      <description>Hi, turns out some mis-configuration by platform admin team. instead of $id@$ud they used $ud@$id while setting up virtual proxy. such a small error was hard to recognize. Thanks anyway for your help.</description>
      <pubDate>Fri, 01 Mar 2019 17:12:37 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Scalability/Qlik-Sense-header-based-authentication-for-health-check-API/m-p/1551220#M1576</guid>
      <dc:creator>ganeshkale</dc:creator>
      <dc:date>2019-03-01T17:12:37Z</dc:date>
    </item>
  </channel>
</rss>

