hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andras Bokor (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-14229) hadoop.security.auth_to_local example is incorrect in the documentation
Date Tue, 25 Apr 2017 15:12:04 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-14229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Andras Bokor updated HADOOP-14229:
    Attachment: HADOOP-14229.03.patch


That is true. Skipping FQDN causes super *group* access between clusters (in the same realm).
I think here we are not intended to provide a production ready mapping it should just be an
example showing what is the basic syntax.
Anyway, your comment made me feel I should provide a bit more complex (but not too complex)
example to show the syntax of auth_to_local rules.

> hadoop.security.auth_to_local example is incorrect in the documentation
> -----------------------------------------------------------------------
>                 Key: HADOOP-14229
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14229
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Andras Bokor
>            Assignee: Andras Bokor
>         Attachments: HADOOP-14229.01.patch, HADOOP-14229.02.patch, HADOOP-14229.03.patch
> Let's see jhs as example:
> {code}RULE:[2:$1@$0](jhs/.*@.*REALM.TLD)s/.*/mapred/{code}
> That means principal has 2 components (jhs/myhost@REALM).
> The second column converts this to jhs@REALM. So the regex will not match on this since
regex expects / in the principal.
> My suggestion is
> {code}RULE:[2:$1](jhs)s/.*/mapred/{code}
> https://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-common/SecureMode.html

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message