[
https://issues.apache.org/jira/browse/AMBARI-21418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16089663#comment-16089663
]
Hadoop QA commented on AMBARI-21418:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12877537/AMBARI-21418.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 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11798//console
This message is automatically generated.
> Ambari rebuilds custom auth_to_local rules changing its case sensitiveness
> option (/L) depending on the case_insensitive_username_rules.
> ----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-21418
> URL: https://issues.apache.org/jira/browse/AMBARI-21418
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.0
> Reporter: Tomas Sokorai
> Assignee: Attila Magyar
> Fix For: 2.5.2
>
> Attachments: AMBARI-21418.patch
>
>
> Ambari changes the auth to local custom rules /L state on rebuild depending
> on case_insensitive_username_rules.
> How to reproduce:
> 1) Kerberize Ambari.
> 2) Make sure these kerberos settings are set as follows:
> case_insensitive_username_rules = false
> manage_auth_to_local = true
> 3) Add custom auth_to_local rule:
> {code:java}
> RULE:[1:$1@$0](.*@HDP01.LOCAL)s/.*/ambari-qa//L
> {code}
> (NB: HDP01.LOCAL realm was chosen to avoid matching the default kerberos
> realm, EXAMPLE.COM in my tests)
> 4) Add a new service to the cluster that has kerberos configuration, in my
> case, tested with adding Spark2.
> 5) After successful service addition, check the auth_to_local mappings again;
> the mapping we added in point 3 should now be missing the /L and be:
> {code:java}
> RULE:[1:$1@$0](.*@HDP01.LOCAL)s/.*/ambari-qa/
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
