[
https://issues.apache.org/jira/browse/AMBARI-16875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15305187#comment-15305187
]
Hadoop QA commented on AMBARI-16875:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12806711/AMBARI-16875.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.state.stack.ConfigUpgradeValidityTest
org.apache.ambari.server.controller.internal.HostResourceProviderTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7044//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7044//console
This message is automatically generated.
> LDAP sync cannot handle if the member attribute value is not DN or id
> ---------------------------------------------------------------------
>
> Key: AMBARI-16875
> URL: https://issues.apache.org/jira/browse/AMBARI-16875
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Olivér Szabó
> Assignee: Olivér Szabó
> Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-16875.patch
>
>
> in case of member attribute value looks like this:
> "<SID=...>;<GUID=...>;cn=myCn,dc=apache,dc=org", then sync stop working.
> adding 2 new properties (to find the dn or the id of the member):
> {{"authentication.ldap.sync.userMemberReplacePattern"}}
> {{"authentication.ldap.sync.groupMemberReplacePattern"}}
> These values are empty by default.
> Example usage:
> If we got this as ldapsearch response for group member
> "member="<SID=...>;<GUID=...>;cn=myCn,dc=apache,dc=org",
> We need to define a regex which contains member group to specify the location
> of the DN or id e.g.{{(?<member>.\*)}}
> authentication.ldap.sync.userMemberReplacePattern={{(?<sid>.\*);(?<guid>.\*);(?<member>.\*)}}
> Then the result will be: "cn=myCn,dc=apache,dc=org"
> also added 2 another new properties for alternative solution:
> {{"authentication.ldap.sync.userMemberFilter"}}
> {{"authentication.ldap.sync.groupMemberFilter"}}
> These values are also empty by default.
> Example usage:
> memberUid=mymemberId
> then you can specify the filter for user sync:
> {{"authentication.ldap.sync.userMemberFilter=(&(objectclass=posixaccount)(uid=\{member\}))"}}
> That filter will be used (with the baseDN) for gather user with the memberUid:
> {{(&(objectclass=posixaccount)(uid=mymemberid))}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
