[ https://issues.apache.org/jira/browse/AMBARI-18664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15605778#comment-15605778 ]
Hudson commented on AMBARI-18664: --------------------------------- FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5866 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5866/]) AMBARI-18664. While syncing with LDAP, username collisions should be (rlevas: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b67d8832108cf5874bddf1a6ccc186fa5ca69e85]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/ldap/AmbariLdapDataPopulator.java * (edit) ambari-server/src/main/python/ambari_server/setupSecurity.py * (edit) ambari-server/src/main/java/org/apache/ambari/server/security/ldap/LdapBatchDto.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/security/ldap/AmbariLdapDataPopulatorTest.java * (edit) ambari-server/docs/configuration/index.md * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/LdapSyncEventResourceProvider.java * (edit) ambari-server/src/main/python/ambari-server.py * (edit) ambari-server/src/test/python/TestAmbariServer.py * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/LdapSyncEventEntity.java > 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, AMBARI-18664_branch-2.5_03.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)