[
https://issues.apache.org/jira/browse/AMBARI-17444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-17444:
----------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
committed to trunk:
{code:java}
commit 740c6caa9be975da87084f4c5b6d5ce4e4c9b543
Author: oleewere <[email protected]>
Date: Tue Jun 28 15:11:51 2016 +0200
AMBARI-17444. LDAP sync: force to use uid and cn in patterns to check a
member is a dn or not (oleewere)
{code}
comitted to branch-2.4:
{code:java}
commit bc8bd587321bd81ba433146ee269a8a21f18bda3
Author: oleewere <[email protected]>
Date: Tue Jun 28 15:11:51 2016 +0200
AMBARI-17444. LDAP sync: force to use uid and cn in patterns to check a
member is a dn or not (oleewere)
{code}
> LDAP sync: use uid and cn in patterns to check a member is a dn or not and
> small fixes
> --------------------------------------------------------------------------------------
>
> Key: AMBARI-17444
> URL: https://issues.apache.org/jira/browse/AMBARI-17444
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Olivér Szabó
> Assignee: Olivér Szabó
> Fix For: 2.4.0
>
> Attachments: AMBARI-17444.patch
>
>
> - fix member dn format check
> - add new attribute: {{authorization.ldap.adminGroupMappingMemberAttr}} what
> can be used during adminGroupMapping rules filter (the filter starts with
> e.g. : member={dn}...if memberUid is used, dn is not right, so you can use
> custom attribute here, like: uid)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
