[
https://issues.apache.org/jira/browse/RANGER-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957382#comment-14957382
]
Don Bosco Durai commented on RANGER-684:
----------------------------------------
[~spolavarapu], I really like the simplicity of this approach. Do you feel we
will need multiple expressions? If so, we need to change the properties to
accept multiple strings.
Can I also suggest we can have this regex implementation implement from a
standard interface? By default, the implementation would be RegEx, but if the
user wants, they can have their complex mapping implementation.
Also, if we are going to use interface, then we should change the property
names. e.g. ranger.usersync.username.mapping.handler
Thanks
> 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)
