[
https://issues.apache.org/jira/browse/HADOOP-6299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12806114#action_12806114
]
Owen O'Malley commented on HADOOP-6299:
---------------------------------------
Java "public" does *not* imply public API. As a concrete instance of that, all
of the RPC protocol interfaces are Java public and none of them are considered
public APIs. Another instance is the NameNode and DataNode classes.
I agree that prior to having the Audience annotations, it wasn't clear who the
intended audience is. We are making progress in marking APIs, but it is not
complete.
> Use JAAS LoginContext for our login
> -----------------------------------
>
> Key: HADOOP-6299
> URL: https://issues.apache.org/jira/browse/HADOOP-6299
> Project: Hadoop Common
> Issue Type: Improvement
> Components: security
> Reporter: Arun C Murthy
> Assignee: Owen O'Malley
> Fix For: 0.22.0
>
> Attachments: 6299-MR-early.patch, h-6299.patch, h-6299.patch,
> h-6299.patch, h-6299.patch, h-6299.patch, HADOOP-6299-2.patch,
> UserGroupInformation.java, UserGroupInformation.java
>
>
> Currently we use a custom login module in UnixUserGroupInformation for
> acquiring user-credentials (via config or exec'ing 'whoami'). We should
> switch to using standard JAAS components such as LoginContext and possibly
> implement a custom UnixLoginContext for our current requirements. In future
> we can use this for Kerberos etc.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
