[
https://issues.apache.org/jira/browse/AMBARI-8984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14264505#comment-14264505
]
Hadoop QA commented on AMBARI-8984:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12690065/AMBARI-8984.patch
against trunk revision .
{color:red}-1 patch{color}. Trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/1157//console
This message is automatically generated.
> Ambari user+group sync does not work with Active Directory
> ----------------------------------------------------------
>
> Key: AMBARI-8984
> URL: https://issues.apache.org/jira/browse/AMBARI-8984
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 1.7.0
> Reporter: Yurii Shylov
> Assignee: Yurii Shylov
> Fix For: 2.0.0
>
> Attachments: AMBARI-8984.patch
>
>
> Ambari LDAP sync does not work with AD where uid is set to null.
> Steps to reproduce:
> Try syncing ldap users from AD and you will see messages like:
> {code}
> 17:19:42,915 WARN [pool-1-thread-1] AmbariLdapDataPopulator:560 - Ignoring
> LDAP user cn=Ambari Admin,ou=Ambari,dc=SME,dc=support,dc=com as it doesn't
> have required attributes uid and sAMAccountName
> 17:20:38,375 WARN [pool-1-thread-2] AmbariLdapDataPopulator:560 - Ignoring
> LDAP user cn=testUser,ou=Ambari,dc=SME,dc=support,dc=com as it doesn't have
> required attributes uid and sAMAccountName
> 17:21:47,387 WARN [pool-1-thread-3] AmbariLdapDataPopulator:560 - Ignoring
> LDAP user cn=testUser,ou=Ambari,dc=SME,dc=support,dc=com as it doesn't have
> required attributes uid and sAMAccountName
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
