<?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 EDX Security in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/EDX-Security/m-p/769547#M273274</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am using the EDF functionality to allow dynamic rebuilds of documents on the AccessPoint.&lt;/P&gt;&lt;P&gt;When I went to put my app into production, I noticed that I had to give the user full access to the production&lt;/P&gt;&lt;P&gt;server in order for EDX submission to work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;While this allows EDX to work, I don't want the user to have access to the QMC on that server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does anyone have experience with this problem ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I believe I have to do either one of these two possible solutions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create a separate AD Group, then:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Restrict access to the QMC url somehow.&lt;/P&gt;&lt;P&gt;or&lt;/P&gt;&lt;P&gt;2. Explicitly grant access to the port(4799) only&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does this make sense ? I'm not actually sure that either of these can be done.&lt;/P&gt;&lt;P&gt;Once I have a proposed solution, I need to submit it to our IT Infrastructure team&lt;/P&gt;&lt;P&gt;to implement.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for any help you can provide.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tim Roy&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 09 Feb 2015 15:13:42 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2015-02-09T15:13:42Z</dc:date>
    <item>
      <title>EDX Security</title>
      <link>https://community.qlik.com/t5/QlikView/EDX-Security/m-p/769547#M273274</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am using the EDF functionality to allow dynamic rebuilds of documents on the AccessPoint.&lt;/P&gt;&lt;P&gt;When I went to put my app into production, I noticed that I had to give the user full access to the production&lt;/P&gt;&lt;P&gt;server in order for EDX submission to work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;While this allows EDX to work, I don't want the user to have access to the QMC on that server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does anyone have experience with this problem ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I believe I have to do either one of these two possible solutions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create a separate AD Group, then:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Restrict access to the QMC url somehow.&lt;/P&gt;&lt;P&gt;or&lt;/P&gt;&lt;P&gt;2. Explicitly grant access to the port(4799) only&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does this make sense ? I'm not actually sure that either of these can be done.&lt;/P&gt;&lt;P&gt;Once I have a proposed solution, I need to submit it to our IT Infrastructure team&lt;/P&gt;&lt;P&gt;to implement.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for any help you can provide.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tim Roy&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Feb 2015 15:13:42 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/EDX-Security/m-p/769547#M273274</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2015-02-09T15:13:42Z</dc:date>
    </item>
  </channel>
</rss>

