[
https://issues.apache.org/jira/browse/RANGER-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14953653#comment-14953653
]
Sailaja Polavarapu commented on RANGER-684:
-------------------------------------------
Looks like while configuring auth_to_local property in core-site.xml, there is
an option "L" that can be configured as part of the rule for converting the
resulted string to lower case. In Ranger, we have a separate property for case
conversion (ranger.usersync.ldap.username.caseconversion &
ranger.usersync.ldap.groupname.caseconversion).
While configuring this new ranger property for special character replacement,
it is better to support the "L" or "U" option for case conversion to be in sync
with hadoop implementation?
> Ranger Usersync - Add Ability to transform user/group names
> -----------------------------------------------------------
>
> Key: RANGER-684
> URL: https://issues.apache.org/jira/browse/RANGER-684
> Project: Ranger
> Issue Type: Improvement
> Affects Versions: 0.4.0, 0.5.0
> Reporter: Velmurugan Periasamy
> Assignee: Sailaja Polavarapu
> Priority: Critical
> Fix For: 0.5.1, 0.6.0
>
>
> Ensure the UserSync is capable of transforming user/group names from LDAP/AD
> source. Probably by allowing custom mapping ( like space to underscore)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
