[
https://issues.apache.org/jira/browse/HADOOP-8455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13412582#comment-13412582
]
Owen O'Malley commented on HADOOP-8455:
---------------------------------------
This is already possible, by using the auth_to_local mapping. The cluster
operator can define arbitrary mappings between long (FOO@DOMAIN) and short
names (DOMAINFOO).
See http://hortonworks.com/blog/fine-tune-your-apache-hadoop-security-settings/
> Address user name format on domain joined Windows machines
> ----------------------------------------------------------
>
> Key: HADOOP-8455
> URL: https://issues.apache.org/jira/browse/HADOOP-8455
> Project: Hadoop Common
> Issue Type: Bug
> Components: native
> Affects Versions: 1.1.0, 0.24.0
> Reporter: Chuan Liu
> Assignee: Ivan Mitic
> Priority: Minor
>
> For a domain joined Windows machine, user name along is not a unique
> identifier. User name plus domain name is need in order to unique identify
> the user. For example, we can have both ‘Win1\Alex’ and ‘Redmond\Alex’ on a
> computer named Win1 that joins Redmond domain. In order to avoid ambiguity,
> ‘whoami’ on Windows and the new ‘winutils’ created in
> [Hadoop-8235|https://issues.apache.org/jira/browse/HADOOP-8235] both return
> [domain]\[username] as the username. In Hadoop, we only use user name right
> now. This may lead to some inconsistency, and production bugs if users of the
> same name exist on the machine.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
