ranger-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sailaja Polavarapu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (RANGER-684) Ranger Usersync - Add Ability to transform user/group names
Date Tue, 13 Oct 2015 18:55:05 GMT

    [ https://issues.apache.org/jira/browse/RANGER-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14955466#comment-14955466

Sailaja Polavarapu commented on RANGER-684:

Introducing two additional (custom) properties:

If the properties are defined, they should be used to transform user/group name after it is
retrieved from the source.

The value for these properties should be in the following format (similar to Sed format):

s – stands for substitution and is mandatory
/ - delimiter and is mandatory
Regex – regular expression to match
Replacement – value to replace and is optional. If not specified, the found pattern is removed
from the resulting string.
g – for replacing all the occurrences. It is optional and if not specified, default to “g”
as well.

> 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

View raw message