You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2016/10/21 23:06:58 UTC
[jira] [Commented] (AMBARI-18664) While syncing with LDAP, username
collisions should be handled based on configuration value
[ https://issues.apache.org/jira/browse/AMBARI-18664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15596628#comment-15596628 ]
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/12834753/AMBARI-18664_branch-2.5_01.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/8977//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.5_01.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)