<?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: HBase Insufficient Permissions with Kerberos in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/HBase-Insufficient-Permissions-with-Kerberos/m-p/87932#M55210</link>
    <description>&lt;P&gt;Thank you for confirming the details,&lt;BR /&gt;&lt;BR /&gt;Does the subject part of your klist output match the added username in the HBase Superusers configuration precisely?&lt;BR /&gt;&lt;BR /&gt;If your user is in a different realm than the cluster services, is the realm name present as part of HDFS -&amp;gt; Configuration -&amp;gt; 'Trusted Realms'?&lt;BR /&gt;&lt;BR /&gt;Are all commands done as the superuser failing? What HBase shell command/operation specifically is leading to your quoted error?&lt;BR /&gt;&lt;BR /&gt;As to adding groups, it can be done in the same field, except you need to add an '@' prefix to the name. For ex. if your group is cluster_administrators, then add it in as '@cluster_administrators' in the HBase Superusers config. When using usernames, the @ must not be specified. Both approaches should work though.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;P.s. If you'll be relying on groups, ensure all cluster hosts return consistent group lookup output for id &amp;lt;user&amp;gt; commands, as the authorization check is distributed across the cluster roles for HBase.&lt;/P&gt;</description>
    <pubDate>Mon, 18 Mar 2019 10:27:28 GMT</pubDate>
    <dc:creator>Harsh J</dc:creator>
    <dc:date>2019-03-18T10:27:28Z</dc:date>
  </channel>
</rss>

