[
https://issues.apache.org/jira/browse/AMBARI-21910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16167826#comment-16167826
]
Hadoop QA commented on AMBARI-21910:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12887336/AMBARI-21910.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12238//console
This message is automatically generated.
> 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
>
> Attachments: AMBARI-21910.patch
>
>
> As part of RANGER-1735, we are supporting nested groups in ranger usersync.
> For this, 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)
