[
https://issues.apache.org/jira/browse/HADOOP-11683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350096#comment-14350096
]
Arun Suresh commented on HADOOP-11683:
--------------------------------------
[~sunny.cheung], this is definitely an interesting JIRA
I am assuming you are talking about :
{noformat}
[email protected] -> user123
[email protected] -> user789
...
possibly some 200k such entries
{noformat}
It is still possible to do so via the existing rules interface.
Although I agree it would be pretty long.
I do have some reservations against making this is User specified class though.
Considering that this would be user code that would be executed within possibly
critical sections of the HDFS code.
I would consider adding a property such as :
{noformat}
<property>
<name>hadoop.security.auth_to_local.mapping-file</name>
<value>/path/to/some/file</value>
</property>
{noformat}
instead of allowing a user defined class
> Need a plugin API to translate long principal names to local OS user names
> arbitrarily
> --------------------------------------------------------------------------------------
>
> Key: HADOOP-11683
> URL: https://issues.apache.org/jira/browse/HADOOP-11683
> Project: Hadoop Common
> Issue Type: Improvement
> Components: security
> Reporter: Sunny Cheung
>
> We need a plugin API to translate long principal names (e.g.
> [email protected]) to local OS user names (e.g. user123456) arbitrarily.
> For some organizations the name translation is straightforward (e.g.
> [email protected] to john_doe), and the hadoop.security.auth_to_local
> configurable mapping is sufficient to resolve this (see HADOOP-6526).
> However, in some other cases the name translation is arbitrary and cannot be
> generalized by a set of translation rules easily.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
