[
https://issues.apache.org/jira/browse/HADOOP-11683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
roger mak updated HADOOP-11683:
-------------------------------
Attachment: HADOOP-11683.001.patch
I uploaded a patch HADOOP-11683.001.patch for review.
The patch allows HadoopKerberosName to use a user name mapping pluggable API
from parameter, hadoop.security.user.name.mapping, instead of the regular
expression specified in parameter, hadoop.security.auth_to_local.
If user name is not found by the API or hadoop.security.user.mapping is not
set, it will default back to hadoop.security.auth_to_local for compatibility.
Note: Similar to the existing CompositeGroupsMapping class, a new class,
CompositeUserNameMapping, is added to handle multiple mapping providers. Cache
is not introduced in this version yet for simplicity.
> 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
> Assignee: Sunny Cheung
> Attachments: HADOOP-11683.001.patch
>
>
> 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)
