<?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 super strange distribution in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/super-strange-distribution/m-p/415967#M154686</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I just discovered one super strange strange behavior of QV.&lt;/P&gt;&lt;P&gt;If we refer to the following, it's a distribution created for a QVW.&lt;/P&gt;&lt;P&gt;the NTNAME field is actually the &lt;STRONG&gt;CN &lt;/STRONG&gt;object from &lt;STRONG&gt;LDAP&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG alt="1842.jpg" class="jive-image-thumbnail jive-image" onclick="" src="https://community.qlik.com/legacyfs/online/22011_1842.jpg" width="450" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now, take a look at the section access.&lt;/P&gt;&lt;P&gt;user type: All authenticated user.&lt;/P&gt;&lt;P&gt;and it's based on &lt;STRONG&gt;WINDOWS ID&lt;/STRONG&gt; !!!&lt;/P&gt;&lt;P&gt;&lt;IMG alt="1844.jpg" class="jive-image-thumbnail jive-image" onclick="" src="https://community.qlik.com/legacyfs/online/22012_1844.jpg" width="450" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Why are there such a gap? &lt;/P&gt;&lt;P&gt;aren't those distribution supposed to be standardized?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Imagine you have 200 users to distribute to, previously was CN object from LDAP.&lt;/P&gt;&lt;P&gt;and just because we switch to section access, we have to use WINDOWS ID?&lt;/P&gt;&lt;P&gt;isnt that strange? sooooo strange no? &lt;IMG src="https://community.qlik.com/legacyfs/online/emoticons/cry.png" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 18 Sep 2012 08:26:10 GMT</pubDate>
    <dc:creator />
    <dc:date>2012-09-18T08:26:10Z</dc:date>
    <item>
      <title>super strange distribution</title>
      <link>https://community.qlik.com/t5/QlikView/super-strange-distribution/m-p/415967#M154686</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I just discovered one super strange strange behavior of QV.&lt;/P&gt;&lt;P&gt;If we refer to the following, it's a distribution created for a QVW.&lt;/P&gt;&lt;P&gt;the NTNAME field is actually the &lt;STRONG&gt;CN &lt;/STRONG&gt;object from &lt;STRONG&gt;LDAP&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG alt="1842.jpg" class="jive-image-thumbnail jive-image" onclick="" src="https://community.qlik.com/legacyfs/online/22011_1842.jpg" width="450" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now, take a look at the section access.&lt;/P&gt;&lt;P&gt;user type: All authenticated user.&lt;/P&gt;&lt;P&gt;and it's based on &lt;STRONG&gt;WINDOWS ID&lt;/STRONG&gt; !!!&lt;/P&gt;&lt;P&gt;&lt;IMG alt="1844.jpg" class="jive-image-thumbnail jive-image" onclick="" src="https://community.qlik.com/legacyfs/online/22012_1844.jpg" width="450" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Why are there such a gap? &lt;/P&gt;&lt;P&gt;aren't those distribution supposed to be standardized?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Imagine you have 200 users to distribute to, previously was CN object from LDAP.&lt;/P&gt;&lt;P&gt;and just because we switch to section access, we have to use WINDOWS ID?&lt;/P&gt;&lt;P&gt;isnt that strange? sooooo strange no? &lt;IMG src="https://community.qlik.com/legacyfs/online/emoticons/cry.png" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Sep 2012 08:26:10 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/super-strange-distribution/m-p/415967#M154686</guid>
      <dc:creator />
      <dc:date>2012-09-18T08:26:10Z</dc:date>
    </item>
  </channel>
</rss>

