[ https://issues.apache.org/jira/browse/HADOOP-15996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16722046#comment-16722046 ]
Bolke de Bruin commented on HADOOP-15996: ----------------------------------------- Ah ok. HADOOP-12751 was available on 2.x , so this is why I suggested 'compatible'. What do you think the scope of the plugin interface needs to be? Your point #1 seems broader than I anticipated. We could also consider a 'native' plugin available when hadoop-native is installed that uses the C-api. JAVA's kerberos interface deviates from MIT/Heimdal in some areas. It would also offload complexities of properly dealing with auth_to_local rules. > Plugin interface to support more complex usernames in Hadoop > ------------------------------------------------------------ > > Key: HADOOP-15996 > URL: https://issues.apache.org/jira/browse/HADOOP-15996 > Project: Hadoop Common > Issue Type: New Feature > Components: security > Reporter: Eric Yang > Priority: Major > > Hadoop does not allow support of @ character in username in recent security > mailing list vote to revert HADOOP-12751. Hadoop auth_to_local rule must > match to authorize user to login to Hadoop cluster. This design does not > work well in multi-realm environment where identical username between two > realms do not map to the same user. There is also possibility that lossy > regex can incorrectly map users. In the interest of supporting multi-realms, > it maybe preferred to pass principal name without rewrite to uniquely > distinguish users. This jira is to revisit if Hadoop can support full > principal names without rewrite and provide a plugin to override Hadoop's > default implementation of auth_to_local for multi-realm use case. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org