[
https://issues.apache.org/jira/browse/RANGER-898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15215817#comment-15215817
]
rangerqa commented on RANGER-898:
---------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12795804/RANGER-898.patch
against master revision 5702966.
{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 javadoc{color}. There were no new javadoc warning messages.
+1 checkstyle. The patch generated 0 code style errors.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-RANGER-Build/128//testReport/
Console output:
https://builds.apache.org/job/PreCommit-RANGER-Build/128//console
This message is automatically generated.
> Change Ranger's default value for LDAP User / Group Sync Case Conversion
> properties to "none"
> ---------------------------------------------------------------------------------------------
>
> Key: RANGER-898
> URL: https://issues.apache.org/jira/browse/RANGER-898
> Project: Ranger
> Issue Type: Improvement
> Components: usersync
> Affects Versions: 0.5.1
> Reporter: Mehul Parikh
> Assignee: Mehul Parikh
> Priority: Minor
> Fix For: 0.6.0
>
> Attachments: RANGER-898.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)
