You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Mugdha Varadkar (JIRA)" <ji...@apache.org> on 2017/09/08 05:27:00 UTC

[jira] [Updated] (AMBARI-21910) Ranger Usersync config to support nested group evaluation for LDAP Sync source property

     [ https://issues.apache.org/jira/browse/AMBARI-21910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mugdha Varadkar updated AMBARI-21910:
-------------------------------------
    Affects Version/s:     (was: trunk)

> Ranger Usersync config to support nested group evaluation for LDAP Sync source property
> ---------------------------------------------------------------------------------------
>
>                 Key: AMBARI-21910
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21910
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.6.0
>            Reporter: Mugdha Varadkar
>            Assignee: Mugdha Varadkar
>             Fix For: trunk, 2.6.0
>
>
> As part of RANGER-1735, we are supporting nested groups in ranger usersync. For this I introduced one new property "ranger.usersync.ldap.grouphierarchylevels". The value should be an integer with default value as 0. This property should be under Ranger --> Configs --> Ranger User Info --> Group Configs tab.
> This property can be enabled with a flag labelled as "Sync Nested Groups". 
> 1. Default value for this flag is "No"
> 2. This flag is always shown under Group Configs (even when "Enable group Sync" is set to "No")
> 3. If this flag is set to "No", then the value for ranger.usersync.ldap.grouphierarchylevels is hidden and is set to "0". 
> 4. If this flag is set to "Yes", then ranger.usersync.ldap.grouphierarchylevels is shown and allowed to set any integer greater than 0.



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