[
https://issues.apache.org/jira/browse/HADOOP-11683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350846#comment-14350846
]
Leo Liou commented on HADOOP-11683:
-----------------------------------
Interesting idea about the mapping file.
To sync the files on many nodes is still issue, although NFS is one possibility.
Still, the users would either write their own plug-in (to an interface), or
obtain it from some ISV.
It still has to be deployed in a controlled fashion - since users would have to
configure it.
So, maybe I missed the point about the concern for a plug-in in this case.
My other thought is that translation rules are still fairly rigid.
None of us can foresee all the different issues or possibilities in the future.
I would suggest that to delegate this part to a plug-in and not making it a
Hadoop issue is quite attractive.
just my 2 cents.
> 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.
> john....@example.com) to local OS user names (e.g. user123456) arbitrarily.
> For some organizations the name translation is straightforward (e.g.
> john....@example.com 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)
