[
https://issues.apache.org/jira/browse/AMBARI-18971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15692694#comment-15692694
]
Mugdha Varadkar commented on AMBARI-18971:
------------------------------------------
[^AMBARI-18971.patch] committed to branch-2.5:
https://github.com/apache/ambari/commit/c538cd8ac7eb6499167efc999af91c15d70cae38
[^AMBARI-18971-trunk.patch] committed to trunk:
https://github.com/apache/ambari/commit/cb1bce2f5af7f4fa6c55b819b23c53ce342d9a45
> 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-trunk.patch, 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)
