<?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: Only allow access to one qvw from DMZ Web Server in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Only-allow-access-to-one-qvw-from-DMZ-Web-Server/m-p/675062#M1316775</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You could build a landing page that removes or adds authorization, through the QlikView Management API, to a document depending on what webserver it is running on.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You would need to store authorization settings for each application somewhere else.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edit: I believe you would need to use webtickets for this to work or the user could just skip the landing page and go straight to the AccessPoint.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 07 Oct 2014 20:30:05 GMT</pubDate>
    <dc:creator>danielrozental</dc:creator>
    <dc:date>2014-10-07T20:30:05Z</dc:date>
    <item>
      <title>Only allow access to one qvw from DMZ Web Server</title>
      <link>https://community.qlik.com/t5/QlikView/Only-allow-access-to-one-qvw-from-DMZ-Web-Server/m-p/675061#M1316773</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;STRONG&gt;Hi&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have a single server on the internal LAN running QV Server &amp;amp; QV Web Server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the DMZ we have set up a second QV Web Server using IIS that accesses the QV Server over the DMZ firewall to the LAN.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This all works fine but we would like to only allow a single qvw to be accessible from the DMZ QV Web Server using IIS.&amp;nbsp; But to access this &amp;amp; other qvw's when using the LAN QV Web Server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All authentication is done by NFTS / AD and the same AD user will be used whatever Web Server is used.&amp;nbsp; [It would though be acceptable for authentication on the DMZ QV Web Server to use a non AD method]&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Any Suggestions ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards,&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;STRONG&gt;Bill&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Jan 2026 18:19:17 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Only-allow-access-to-one-qvw-from-DMZ-Web-Server/m-p/675061#M1316773</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2026-01-26T18:19:17Z</dc:date>
    </item>
    <item>
      <title>Re: Only allow access to one qvw from DMZ Web Server</title>
      <link>https://community.qlik.com/t5/QlikView/Only-allow-access-to-one-qvw-from-DMZ-Web-Server/m-p/675062#M1316775</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You could build a landing page that removes or adds authorization, through the QlikView Management API, to a document depending on what webserver it is running on.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You would need to store authorization settings for each application somewhere else.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edit: I believe you would need to use webtickets for this to work or the user could just skip the landing page and go straight to the AccessPoint.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Oct 2014 20:30:05 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Only-allow-access-to-one-qvw-from-DMZ-Web-Server/m-p/675062#M1316775</guid>
      <dc:creator>danielrozental</dc:creator>
      <dc:date>2014-10-07T20:30:05Z</dc:date>
    </item>
  </channel>
</rss>

