Return-Path: X-Original-To: apmail-hadoop-mapreduce-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id ED4CE105B0 for ; Fri, 10 Jan 2014 07:59:36 +0000 (UTC) Received: (qmail 89029 invoked by uid 500); 10 Jan 2014 07:57:27 -0000 Delivered-To: apmail-hadoop-mapreduce-user-archive@hadoop.apache.org Received: (qmail 88776 invoked by uid 500); 10 Jan 2014 07:57:10 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 88657 invoked by uid 99); 10 Jan 2014 07:57:03 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Jan 2014 07:57:03 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,WEIRD_PORT X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of nishant.has.a.question@gmail.com designates 209.85.219.54 as permitted sender) Received: from [209.85.219.54] (HELO mail-oa0-f54.google.com) (209.85.219.54) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Jan 2014 07:56:57 +0000 Received: by mail-oa0-f54.google.com with SMTP id o6so4701922oag.27 for ; Thu, 09 Jan 2014 23:56:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=jCb8m3aDfUuaIX6TCcy9DnwZQB+nxWRZo9d49QvRQc8=; b=TcjWdRn3AO+P0EY3ubB11Bn24Cizf3te24SB1hyhjeVhfZL83Vwlgun6qflbXugVSV 0oEtfTu1tL8ONB680In8feT8dzwddvCcnxoZZh3fZ4FlaMUp5hZC30VMDywMJOayovVr DjhR3+W9VZ90oPGWZ0lSx8sKww5BeQoNxPQKfCpOc0ZtKpyuAWNOEY8+74CnUR0KFNs1 H/Q67PnCLEoo4OQ24j/Q0HzUR8EOU8g2dYewYthqYzBYCnqII4B4jVQE4k/GILgEDyaO gvytc3aw3ykAc0glHDUdyAYEVR3mPmnESWEV0tXIGNgcvBO2GD6n/8awM1uPgB8+0HWb 4Txg== MIME-Version: 1.0 X-Received: by 10.182.158.71 with SMTP id ws7mr6428489obb.6.1389340596688; Thu, 09 Jan 2014 23:56:36 -0800 (PST) Received: by 10.76.195.43 with HTTP; Thu, 9 Jan 2014 23:56:36 -0800 (PST) Date: Fri, 10 Jan 2014 13:26:36 +0530 Message-ID: Subject: HDFS authentication From: Pinak Pani To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=089e01494a16bcdc6304ef99102d X-Virus-Checked: Checked by ClamAV on apache.org --089e01494a16bcdc6304ef99102d Content-Type: text/plain; charset=ISO-8859-1 Does HDFS provide any build in authentication out of the box? I wanted to make explicit access to HDFS from Java. I wanted people to access HDFS using "username:password@hdfs://client.skynet.org:9000/user/data" or something like that. I am new to Hadoop. We are planning to use Hadoop mainly for Archiving and probably processing at a later time. The idea is customers can setup their own HDFS cluster and provide us the HDFS URL to dump the data to. Is it possible to have access to HDFS in a similar way we access databases using credential? Thanks. --089e01494a16bcdc6304ef99102d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Does HDFS provide any build in authentication out of = the box? I wanted to make explicit access to HDFS from Java. I wanted peopl= e to access HDFS using "username:password@hdfs://client.skynet.org:9000/user/data" o= r something like that.

I am new to Hadoop. We are planning to use Hadoop mainl= y for Archiving and probably processing at a later time. The idea is custom= ers can setup their own HDFS cluster and provide us the HDFS URL to dump th= e data to.

Is it possible to have access to HDFS in a similar way = we access databases using credential?

Thanks.
--089e01494a16bcdc6304ef99102d--