You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Jayush Luniya (JIRA)" <ji...@apache.org> on 2016/05/26 06:11:12 UTC

[jira] [Commented] (AMBARI-16813) Ranger Usersync config to support Group Based Search for LDAP Sync Source

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

Jayush Luniya commented on AMBARI-16813:
----------------------------------------

Branch-2.4
commit c22547d009415239eab27c4318d073b70a1bd3d5
Author: Jayush Luniya <jl...@hortonworks.com>
Date:   Wed May 25 23:09:50 2016 -0700

    AMBARI-16813 Ranger Usersync config to support Group Based Search for LDAP Sync Source (Mugdha Varadkar via jluniya


> Ranger Usersync config to support Group Based Search for LDAP Sync Source
> -------------------------------------------------------------------------
>
>                 Key: AMBARI-16813
>                 URL: https://issues.apache.org/jira/browse/AMBARI-16813
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Mugdha Varadkar
>            Assignee: Mugdha Varadkar
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-16813.patch
>
>
> For Stack 2.5 onwards Ranger Usersync is supporting Group based search.
> Need to add below two properties:
> ranger.usersync.group.search.first.enabled=false
> ranger.usersync.user.searchenabled=false
> Proposed flow for Erie:
> 1. ranger.usersync.group.search.first.enabled=false (by default) under Group configs tab -- Can be always available or can be available & configurable when ranger.usersync.group.searchenabled=true
> 2. ranger.usersync.user.searchenabled=false (by default) under User configs tab
>        -- Should be greyed out or hidden when ranger.usersync.group.search.first.enabled=false
>        -- Should be configurable when ranger.usersync.group.search.first.enabled=true



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)