[ https://issues.apache.org/jira/browse/AMBARI-18664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15602835#comment-15602835 ]
Hadoop QA commented on AMBARI-18664: ------------------------------------ {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12834969/AMBARI-18664_branch-2.5_02.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 2 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.controller.internal.UpgradeResourceProviderTest Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/8990//testReport/ Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/8990//console This message is automatically generated. > While syncing with LDAP, username collisions should be handled based on > configuration value > ------------------------------------------------------------------------------------------- > > Key: AMBARI-18664 > URL: https://issues.apache.org/jira/browse/AMBARI-18664 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Affects Versions: 2.0.0 > Reporter: Robert Levas > Assignee: Robert Levas > Fix For: 2.4.2 > > Attachments: AMBARI-18664_branch-2.4_01.patch, > AMBARI-18664_branch-2.4_02.patch, AMBARI-18664_branch-2.5_01.patch, > AMBARI-18664_branch-2.5_02.patch > > > While syncing with LDAP, username collisions should be handled based on an > LDAP sync configuration value. > The configuration options should be to indicate the following behaviors > * convert > ** convert the existing (non-LDAP user) user to an LDAP user > ** This is the existing behavior > * skip > ** skip or ignore the collision, leaving the existing user unchanged > ** a new user record should not be created > Note: Future behavior may be to cause the sync operation to fail, but that > shouldn't be handed yet. > This configuration value should be set when setting up LDAP sync properties > via {{ambari-server setup-ldap}} and be enforced when processing the sync > operation in methods like > {{org.apache.ambari.server.controller.AmbariManagementControllerImpl#synchronizeLdapUsersAndGroups}} > or {{org.apache.ambari.server.security.authorization.Users#processLdapSync}}. -- This message was sent by Atlassian JIRA (v6.3.4#6332)