Return-Path: <common-issues-return-110748-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org>
X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
	by cust-asf2.ponee.io (Postfix) with ESMTP id CC65A200B11
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Mon, 30 May 2016 08:08:14 +0200 (CEST)
Received: by cust-asf.ponee.io (Postfix)
	id CB132160A2C; Mon, 30 May 2016 06:08:14 +0000 (UTC)
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by cust-asf.ponee.io (Postfix) with SMTP id 21917160A07
	for <archive-asf-public@cust-asf.ponee.io>; Mon, 30 May 2016 08:08:13 +0200 (CEST)
Received: (qmail 51154 invoked by uid 500); 30 May 2016 06:08:13 -0000
Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:common-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:common-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:common-issues@hadoop.apache.org>
List-Id: <common-issues.hadoop.apache.org>
Delivered-To: mailing list common-issues@hadoop.apache.org
Received: (qmail 51138 invoked by uid 99); 30 May 2016 06:08:13 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 May 2016 06:08:13 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id 03AE42C14F8
	for <common-issues@hadoop.apache.org>; Mon, 30 May 2016 06:08:13 +0000 (UTC)
Date: Mon, 30 May 2016 06:08:13 +0000 (UTC)
From: "Vinayakumar B (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12948684.1457592698000.329759.1464588493011@Atlassian.JIRA>
In-Reply-To: <JIRA.12948684.1457592698000@Atlassian.JIRA>
References: <JIRA.12948684.1457592698000@Atlassian.JIRA> <JIRA.12948684.1457592698157@arcas>
Subject: [jira] [Commented] (HADOOP-12911) Upgrade Hadoop MiniKDC with Kerby
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
archived-at: Mon, 30 May 2016 06:08:15 -0000


    [ https://issues.apache.org/jira/browse/HADOOP-12911?page=3Dcom.atlassi=
an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D15=
306272#comment-15306272 ]=20

Vinayakumar B commented on HADOOP-12911:
----------------------------------------

I am sorry for coming in late for this,
I have one quick comment/suggestion, can be fixed in follow up jira.
{code}<groupId>org.apache.kerby</groupId>
<artifactId>kerb-simplekdc</artifactId>
<version>1.0.0-RC2</version>{code}
{{hadoop-project/pom.xml}} contains the dependencies of all libraries used =
in all modules of hadoop,  under {{dependencyManagement}}. Only here {{vers=
ion}} will be mentioned. All other Hadoop Modules will inherit {{hadoop-pro=
ject}}, so all submodules will use the same version. In submodule, {{versio=
n}} need not be mentioned in pom.xml. This will make version management eas=
ier.

> Upgrade Hadoop MiniKDC with Kerby
> ---------------------------------
>
>                 Key: HADOOP-12911
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12911
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: test
>            Reporter: Jiajia Li
>            Assignee: Jiajia Li
>             Fix For: 3.0.0-alpha1
>
>         Attachments: HADOOP-12911-v1.patch, HADOOP-12911-v2.patch, HADOOP=
-12911-v3.patch, HADOOP-12911-v4.patch, HADOOP-12911-v5.patch, HADOOP-12911=
-v6.patch, HADOOP-12911-v7.patch, HaDOOP-12911-v8.patch
>
>
> As discussed in the mailing list, we=E2=80=99d like to introduce Apache K=
erby into Hadoop. Initially it=E2=80=99s good to start with upgrading Hadoo=
p MiniKDC with Kerby offerings. Apache Kerby (https://github.com/apache/dir=
ectory-kerby), as an Apache Directory sub project, is a Java Kerberos bindi=
ng. It provides a SimpleKDC server that borrowed ideas from MiniKDC and imp=
lemented all the facilities existing in MiniKDC. Currently MiniKDC depends =
on the old Kerberos implementation in Directory Server project, but the imp=
lementation is stopped being maintained. Directory community has a plan to =
replace the implementation using Kerby. MiniKDC can use Kerby SimpleKDC dir=
ectly to avoid depending on the full of Directory project. Kerby also provi=
des nice identity backends such as the lightweight memory based one and the=
 very simple json one for easy development and test environments.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org