[
https://issues.apache.org/jira/browse/AMBARI-15153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15171865#comment-15171865
]
Hadoop QA commented on AMBARI-15153:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12790398/AMBARI-15153.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/5616//console
This message is automatically generated.
> Change Ranger's default value for LDAP Group Sync Case Conversion properties
> to "none"
> --------------------------------------------------------------------------------------
>
> Key: AMBARI-15153
> URL: https://issues.apache.org/jira/browse/AMBARI-15153
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.2.0
> Reporter: Gautam Borad
> Assignee: Gautam Borad
> Fix For: 2.4.0
>
> Attachments: AMBARI-15153.patch
>
>
> *Use Case:*
> If user's LDAP / AD has uppercase usernames and produce uppercase user
> Kerberos principals. When doing the initial user sync into Ranger, the
> default setting of "lower" causes all their user names to be saved in lower
> case, meaning they don't match the Kerberos principals that LDAP / AD is
> handing out.
> It seems to me the more sensible default for both username and group case
> conversion should be "none" and to just use whatever the backend directory
> hands out, as-is, to prevent unexpected confusion such as this.
> *Proposed Solution:*
> Change Ranger's default settings for below given properties :
> ldapGroupSync.username.caseConversion = "none"
> ldapGroupSync.groupname.caseConversion = "none"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
