Return-Path: X-Original-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-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 DD42DDCBA for ; Wed, 28 Nov 2012 09:07:54 +0000 (UTC) Received: (qmail 18060 invoked by uid 500); 28 Nov 2012 09:07:50 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 17960 invoked by uid 500); 28 Nov 2012 09:07:49 -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 17945 invoked by uid 99); 28 Nov 2012 09:07:49 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Nov 2012 09:07:49 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of harsh@cloudera.com designates 209.85.223.176 as permitted sender) Received: from [209.85.223.176] (HELO mail-ie0-f176.google.com) (209.85.223.176) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Nov 2012 09:07:43 +0000 Received: by mail-ie0-f176.google.com with SMTP id 13so15001134iea.35 for ; Wed, 28 Nov 2012 01:07:23 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding:x-gm-message-state; bh=1KWULKna1wEfgdL9N6ozZi6QuhZRxWOElFOz3fdJQz4=; b=AZ00b0Yj5Af8E7NlzJBXB1MqHaIbbtHK7qJtsI6lasBUsG9d7GtwYrA1rh/R1Pl/CE BPS2Dv+ErxQFQ5QIcMjNbBWNnnysLG8gBwBpHwatPJxhD3hXHuavALIMjnTrPjqu5GQ1 pe3ipgRkAd9jDoGFSs7mpTtnF/3RFbjDNMAePQxdTuDpark8zvFJyiYJR16gcHZrVQI/ +Ljn6uFvLefd2qz2PL7VbiZU02cVjcORafE3ATZ9QVY581e5VKb2lhtPhSASa1se0Mlv GbgwNNnHXrJlDUuSZXb7K90078lsDYjPAFdouY/NMzw71JAhcXKKOkgDaxWOm/rlEQAk O/8Q== Received: by 10.50.185.230 with SMTP id ff6mr18285626igc.7.1354093642969; Wed, 28 Nov 2012 01:07:22 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.6.129 with HTTP; Wed, 28 Nov 2012 01:06:59 -0800 (PST) In-Reply-To: References: From: Harsh J Date: Wed, 28 Nov 2012 14:36:59 +0530 Message-ID: Subject: Re: Could I authenticate hadoop manually using kerberos To: "" Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQkRBYSoMmDAF9UQJWSi9c6k0U9WYH84u+28ygMnssuULevOn111UXFOGpu6aYYZ0jSl2QTF X-Virus-Checked: Checked by ClamAV on apache.org If the cluster is secured, it will demand kerberos credentials. There is no way to bypass this requirement (and it wouldn't make sense to allow such a thing either). If you do have a keytab file, and are wishing to automate the login by knowing the keytab path, you can use the SecurityUtil.login(=85) API: http://hadoop.apache.org/docs/stable/api/org/apache/hadoop/security/Securit= yUtil.html#login(org.apache.hadoop.conf.Configuration,%20java.lang.String,%= 20java.lang.String) On Wed, Nov 28, 2012 at 2:27 PM, Oh Seok Keun wrote: > HI. > > I set my hadoop cluster to security enable using kerberos. > Can I login to the hadoop cluster without execute kinit command? > I can't find hadoop api that I use kerberos principal (manually set > username and password) instead cached ticket. > How can I use hadoop api for that. > > thanks. > > -- > ----------------------------- > ohsg74@gmail.com > H.P.: 010-2534-6795 > ------------------------------ --=20 Harsh J