<?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>question Re: Ranger policies not working for some groups in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ranger-policies-not-working-for-some-groups/m-p/213228#M63291</link>
    <description>&lt;P&gt;The problem was with case conversion. I got firstly Upper case conversion for groups, then created some policies, then changed to none conversion, but in .json files were still appearing Upper case converted group names&lt;/P&gt;</description>
    <pubDate>Tue, 20 Jun 2017 22:08:34 GMT</pubDate>
    <dc:creator>frank93</dc:creator>
    <dc:date>2017-06-20T22:08:34Z</dc:date>
    <item>
      <title>Ranger policies not working for some groups</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ranger-policies-not-working-for-some-groups/m-p/213227#M63290</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I have a strange problem. I have configured Ranger Usersync with AD and it works good. All groups, users and group membership are synced correctly. Problem scenario: user1 belongs to groups group1 and group2. When I create policy (no matter what kind of - hdfs, hive, hbase) for group1, user1 has access. But when I create policy for group2, user1 does not have access. Both groups are returned when I run "hdfs groups user1". In Ranger GUI user1 belongs to both groups. The cluster was Kerberized one week ago, and I do not remember if both groups were working before Kerberos. HDP2.5 and Ranger 0.6.0. This is not a sandbox cluster. There are no errors in ranger/usersync logs.&lt;/P&gt;&lt;P&gt;Do you have any ideas?&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jun 2017 19:04:15 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ranger-policies-not-working-for-some-groups/m-p/213227#M63290</guid>
      <dc:creator>frank93</dc:creator>
      <dc:date>2017-06-20T19:04:15Z</dc:date>
    </item>
    <item>
      <title>Re: Ranger policies not working for some groups</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ranger-policies-not-working-for-some-groups/m-p/213228#M63291</link>
      <description>&lt;P&gt;The problem was with case conversion. I got firstly Upper case conversion for groups, then created some policies, then changed to none conversion, but in .json files were still appearing Upper case converted group names&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jun 2017 22:08:34 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ranger-policies-not-working-for-some-groups/m-p/213228#M63291</guid>
      <dc:creator>frank93</dc:creator>
      <dc:date>2017-06-20T22:08:34Z</dc:date>
    </item>
    <item>
      <title>Re: Ranger policies not working for some groups</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ranger-policies-not-working-for-some-groups/m-p/213229#M63292</link>
      <description>&lt;P&gt;Can you specify the location of json files which needs to be checked.&lt;/P&gt;</description>
      <pubDate>Mon, 28 May 2018 20:56:24 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ranger-policies-not-working-for-some-groups/m-p/213229#M63292</guid>
      <dc:creator>bhanu_pamu</dc:creator>
      <dc:date>2018-05-28T20:56:24Z</dc:date>
    </item>
  </channel>
</rss>

