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 2016/11/23 10:01:11 UTC
[jira] [Updated] (AMBARI-18971) Populate Ranger LDAP group configs
under LDAP category used for authentication
[ https://issues.apache.org/jira/browse/AMBARI-18971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mugdha Varadkar updated AMBARI-18971:
-------------------------------------
Attachment: AMBARI-18971.patch
> 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)