Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Fri, 23 Aug 2013 00:45:52 +0000 (UTC)
From: "Larry McCay (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12660595.1375173338301.20805.1377218752355@arcas>
In-Reply-To: <JIRA.12660595.1375173338301@arcas>
References: <JIRA.12660595.1375173338301@arcas>
Subject: [jira] [Commented] (HADOOP-9797) Pluggable and compatible UGI
 change
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/HADOOP-9797?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D137=
48145#comment-13748145 ]=20

Larry McCay commented on HADOOP-9797:
-------------------------------------

In fact, we have to be really careful about changing the client facing APIs=
. For instance, clients - including third parties - leverage static loginUs=
erFromKeyTab methods. It is difficult to impossible to know all the consume=
rs of those APIs. So anyway, that is just a heads-up.
               =20
> Pluggable and compatible UGI change
> -----------------------------------
>
>                 Key: HADOOP-9797
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9797
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: security
>            Reporter: Kai Zheng
>            Assignee: Kai Zheng
>              Labels: Rhino
>             Fix For: 3.0.0
>
>         Attachments: HADOOP-9797-v1.patch
>
>
> As already widely discussed current UGI related classes needs to be impro=
ved in many aspects. This is to improve and make UGI so that it can be:=20
> =20
> * Pluggable, new authentication method with its login module can be dynam=
ically registered and plugged without having to change the UGI class;
> * Extensible, login modules with their options can be dynamically extende=
d and customized so that can be reusable elsewhere, like in TokenAuth;
> =20
> * No Kerberos relevant, remove any Kerberos relevant functionalities out =
of it to make it simple and suitable for other login mechanisms;=20
> * Of appropriate abstraction and API, with improved abstraction and API i=
t=E2=80=99s possible to allow authentication implementations not using JAAS=
 modules;
> * Compatible, should be compatible with previous deployment and authentic=
ation methods, so the existing APIs won=E2=80=99t be removed and some of th=
em are just to be deprecated.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira