[jira] [Commented] (AMBARI-18971) Populate Ranger LDAP group configs under LDAP category used for authentication

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on AMBARI-18971:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12840228/AMBARI-18971.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/9378//console

This message is automatically generated.

> Populate Ranger LDAP group configs under LDAP category used for authentication
> ------------------------------------------------------------------------------
>
>                 Key: AMBARI-18971
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18971
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.0, 2.2.2, 2.4.1, 2.4.2
>            Reporter: Mugdha Varadkar
>            Assignee: Mugdha Varadkar
>            Priority: Critical
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-18971.patch
>
>
> There are two properties under advanced ranger-admin-site called "Group Search Base" and "Group Search Filter" which are auto populated with the ones from Ranger User Info Group config. These are used during ldap authentication.
> It is little confusing as they are hidden somewhere below and user is not aware of these config while configuring other authentication properties



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