Sorry, missed this email earlier. This seems more appropriate for the Hbase
On Wed, Jul 11, 2012 at 8:41 AM, Tony Dean <[EMAIL PROTECTED]> wrote:
> Looking at this further, it appears that when HBaseRPC is creating a proxy
> (e.g., SecureRpcEngine), it injects the current user:
> User.getCurrent() which by default is the cached Kerberos TGT (kinit'ed
> user - using the "hadoop-user-kerberos" JAAS context).
> Since the server proxy always uses User.getCurrent(), how can an
> application inject the user it wants to use for authorization checks on the
> peer (region server)?
> And since SecureHadoopUser is a static class, how can you have more than 1
> active user in the same application?
> What you have works for a single user application like the hbase shell,
> but what about a multi-user application?
> Am I missing something?
> -----Original Message-----
> From: Alejandro Abdelnur [mailto:[EMAIL PROTECTED]]
> Sent: Monday, July 02, 2012 11:40 AM
> To: [EMAIL PROTECTED]
> Subject: Re: hadoop security API (repost)
> If you are doing a server app that interacts with the cluster on behalf of
> different users (like Ooize, as you mentioned in your email), then you
> should use the proxyuser capabilities of Hadoop.
> * Configure user MYSERVERUSER as proxyuser in Hadoop core-site.xml (this
> requires 2 properties settings, HOSTS and GROUPS).
> * Run your server app as MYSERVERUSER and have a Kerberos principal
> * Initialize your server app loading the MYSERVERUSER/MYSERVERHOST keytab
> * Use the UGI.doAs() to create JobClient/Filesystem instances using the
> user you want to do something on behalf
> * Keep in mind that all the users you need to do something on behalf
> should be valid Unix users in the cluster
> * If those users need direct access to the cluster, they'll have to be
> also defined in in the KDC user database.
> Hope this helps.
> On Mon, Jul 2, 2012 at 6:22 AM, Tony Dean <[EMAIL PROTECTED]> wrote:
> > Yes, but this will not work in a multi-tenant environment. I need to be
> able to create a Kerberos TGT per execution thread.
> > I was hoping through JAAS that I could inject the name of the current
> principal and authenticate against it. I'm sure there is a best practice
> for hadoop/hbase client API authentication, just not sure what it is.
> > Thank you for your comment. The solution may well be associated with
> the UserGroupInformation class. Hopefully, other ideas will come from this
> > Thanks.
> > -Tony
> > -----Original Message-----
> > From: Ivan Frain [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, July 02, 2012 8:14 AM
> > To: [EMAIL PROTECTED]
> > Subject: Re: hadoop security API (repost)
> > Hi Tony,
> > I am currently working on this to access HDFS securely and
> > What I have found so far may help even if I am not 100% sure this is the
> right way to proceed.
> > If you have already obtained a TGT from the kinit command, hadoop
> library will locate it "automatically" if the name of the ticket cache
> corresponds to default location. On Linux it is located
> > For example, with my linux user hdfs, I get a TGT for hadoop user 'ivan'
> > meaning you can impersonate ivan from hdfs linux user:
> > ------------------------------------------
> > hdfs@mitkdc:~$ klist
> > Ticket cache: FILE:/tmp/krb5cc_10003
> > Default principal: [EMAIL PROTECTED]
> > Valid starting Expires Service principal
> > 02/07/2012 13:59 02/07/2012 23:59 krbtgt/[EMAIL PROTECTED] renew
> > until 03/07/2012 13:59
> > -------------------------------------------
> > Then, you just have to set the right security options in your hadoop
> client in java and the identity will be [EMAIL PROTECTED] for our example.
> In my tests, I only use HDFS and here a snippet of code to have access to a