On Mon, Jul 2, 2012 at 9:15 AM, Tony Dean <[EMAIL PROTECTED]> wrote:
> Thanks for the reply. My intent is to also be able to scan/get/put hbase tables under a specified identity as well. What options do I have to perform the same multi-tenant authorization for these operations? I have posted this to hbase users distribution list as well, but thought you might have insight. Since hbase security authentication is so dependent upon hadoop, it would be nice if your suggestion worked for hbase as well.
> Getting back to your suggestion... when configuring "hadoop.proxyuser.myserveruser.hosts", host1 would be where I'm making the ugi.doAs() privileged call and host2 is the hadoop namenode?
host1 in that case.
> Also, an another option, is there not a way for an application to pass hadoop/hbase authentication the name of a Kerberos principal to use? In this case, no proxy, just execute as the designated user.
You could do that, but that means your app will have to have keytabs
for all the users want to act as. Proxyuser will be much easier to
manage. Maybe getting proxyuser support in hbase if it is not there
> -----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 MYSERVERUSER/MYSERVERHOST
> * 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 thread.
>> -----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 programmaticaly.
>> 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 /tmp/krb5cc_uid-number.
>> 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 secure hdfs cluster assuming the previous TGT (ivan's impersonation):