You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ranger.apache.org by "Sailaja Polavarapu (JIRA)" <ji...@apache.org> on 2017/08/22 22:57:00 UTC

[jira] [Commented] (RANGER-1632) Users are not sync'd when sAMAccountName is different than CN associated with groups

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

Sailaja Polavarapu commented on RANGER-1632:
--------------------------------------------

Committed changes to master and ranger-0.7 branches.

> Users are not sync'd when sAMAccountName is different than CN associated with groups
> ------------------------------------------------------------------------------------
>
>                 Key: RANGER-1632
>                 URL: https://issues.apache.org/jira/browse/RANGER-1632
>             Project: Ranger
>          Issue Type: Bug
>          Components: Ranger, usersync
>    Affects Versions: 0.7.0
>            Reporter: Sailaja Polavarapu
>            Assignee: Sailaja Polavarapu
>             Fix For: 1.0.0
>
>         Attachments: 0001-RANGER-1632-Fixed-issue-where-Users-are-not-sync-d-w.patch, 0001-RANGER-1632-Fixed-issue-where-Users-are-not-sync-d-w.patch
>
>
> When "Enable Group Search First" is true and "Enable User Search" is true, then users are not sync'd to Ranger where CN of the user is different from sAMAccountName.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)