[ 
https://issues.apache.org/jira/browse/AMBARI-16023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15257495#comment-15257495
 ] 

Hadoop QA commented on AMBARI-16023:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12800597/AMBARI-16023_trunk_01.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:red}-1 core tests{color}.  The test build failed in ambari-server 

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/6647//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/6647//console

This message is automatically generated.

> Auth-to-local rule generation duplicates default rules when adding 
> case-insensitive default rules
> -------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-16023
>                 URL: https://issues.apache.org/jira/browse/AMBARI-16023
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.2.0
>            Reporter: Robert Levas
>            Assignee: Robert Levas
>            Priority: Critical
>              Labels: auth_to_local, kerberos
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-16023_trunk_01.patch
>
>
> When re-generating auth-to-local rules where existing rules are already set, 
> the default (or fallback) rule for the default and additional realms is 
> duplicated but the extra instance(s) have the case-insensitive flag:
> Example:
> {noformat:title=Was}
> ...
> RULE:[1:$1@$0](.*@EXAMPLE.COM)s/@.*//
> ...
> {noformat}
> {noformat:title=Becomes}
> ...
> RULE:[1:$1@$0](.*@EXAMPLE.COM)s/@.*//
> RULE:[1:$1@$0](.*@EXAMPLE.COM)s/@.*///L
> ...
> {noformat}
> *Steps to Reproduce*
> # Create cluster with (at least) HDFS
> # Enable Kerberos (do not check the box next to "Enable case insensitive 
> username rules"; kerberos-env/case_insensitive_username_rules should be false
> # Edit Kerberos configuration and check "Enable case insensitive username 
> rules" to set kerberos-env/case_insensitive_username_rules to true
> # Regenerate Keytabs
> # See duplicate entry in HDFS configs 
> (core-site/hadoop.security.auth_to_local)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to