[
https://issues.apache.org/jira/browse/AMBARI-18813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15648593#comment-15648593
]
Hadoop QA commented on AMBARI-18813:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12838032/AMBARI-18813_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/9180//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9180//console
This message is automatically generated.
> Optionally force username from LDAP authentication data to be lowercase in
> Ambari
> ---------------------------------------------------------------------------------
>
> Key: AMBARI-18813
> URL: https://issues.apache.org/jira/browse/AMBARI-18813
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Robert Levas
> Assignee: Robert Levas
> Labels: ldap
> Fix For: 2.5.0
>
> Attachments: AMBARI-18813_branch-2.5_01.patch,
> AMBARI-18813_trunk_01.patch
>
>
> Optionally force username from LDAP authentication data to be lowercase in
> Ambari based on LDAP import configuration.
> In some cases the username declared in the relevant LDAP object is in all
> uppercase characters when the local Hadoop cluster expects the username to be
> all lowercase. As of Ambari 2.4.0, the username specified from the LDAP data
> is used to override the username known to Ambari. This overwritten data may
> be in all uppercase characters, potentially breaking local username
> conventions.
> To help this scenario, provide a configuration option to force the username
> obtained from the LDAP object to be converted to all lowercase character.
> For example {{authentication.ldap.username.forceLowercase}}.
> This optional configuration value is to default to false to maintain current
> functionality.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
