Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Tue, 24 Feb 2015 11:22:05 +0000 (UTC)
From: "Tom Beerbower (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12777160.1424776683000.527.1424776925049@Atlassian.JIRA>
In-Reply-To: <JIRA.12777160.1424776683000@Atlassian.JIRA>
References: <JIRA.12777160.1424776683000@Atlassian.JIRA>
 <JIRA.12777160.1424776683648@arcas>
Subject: [jira] [Updated] (AMBARI-9767) Provide setup-ldap option option to
 set referral method
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AMBARI-9767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Beerbower updated AMBARI-9767:
----------------------------------
    Attachment: AMBARI-9767.patch

> Provide setup-ldap option option to set referral method
> -------------------------------------------------------
>
>                 Key: AMBARI-9767
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9767
>             Project: Ambari
>          Issue Type: Task
>            Reporter: Tom Beerbower
>            Assignee: Tom Beerbower
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-9767.patch
>
>
> ambari-server sync-ldap fails with certain AD setups. Need to follow referrals. To fix this:
> 1) Have sync-ldap follow referrals = true by default
> 2) expose an optional argument --referrals for users to ignore
> Here is the setup process with:
> {noformat}
> [root@revo1 ~]# rpm -q ambari-server
> ambari-server-2.0.0-426.noarch
> [root@revo1 ~]# ambari-server --hash
> 182b34732350e4a515950bc3667d3824bbd7f15a
> {noformat}
> {noformat}
> [root@revo1 hdfs]# ambari-server setup-ldap
> Using python  /usr/bin/python2.6
> Setting up LDAP properties...
> Primary URL* {host:port} : ad.hortonworks.local:389
> Secondary URL {host:port} : 
> Use SSL* [true/false] (false): 
> User object class* (posixAccount): user
> User name attribute* (uid): sAMAccoutnName
> Group object class* (posixGroup): group
> Group name attribute* (cn): sAMAccountName
> Group member attribute* (memberUid): member
> Distinguished name attribute* (dn): 
> Base DN* : dc=hortonworks,dc=local
> Bind anonymously* [true/false] (false): 
> Manager DN* : CN=hadoopsvc,CN=Users,dc=hortonworks,dc=local
> Enter Manager Password* : 
> Re-enter password: 
> ====================
> Review Settings
> ====================
> authentication.ldap.managerDn: CN=hadoopsvc,CN=Users,dc=hortonworks,dc=local
> authentication.ldap.managerPassword: *****
> Save settings [y/n] (y)? 
> Saving...done
> Ambari Server 'setup-ldap' completed successfully.
> [root@revo1 hdfs]# ambari-server restart
> Using python  /usr/bin/python2.6
> Restarting ambari-server
> Using python  /usr/bin/python2.6
> Stopping ambari-server
> Ambari Server stopped
> Using python  /usr/bin/python2.6
> Starting ambari-server
> Ambari Server running with administrator privileges.
> Organizing resource files at /var/lib/ambari-server/resources...
> Server PID at: /var/run/ambari-server/ambari-server.pid
> Server out at: /var/log/ambari-server/ambari-server.out
> Server log at: /var/log/ambari-server/ambari-server.log
> Waiting for server start....................
> Ambari Server 'start' completed successfully.
> {noformat}
> Here is the sync process
> {noformat}
> [root@revo1 hdfs]# ambari-server sync-ldap --all
> Using python  /usr/bin/python2.6
> Syncing with LDAP...
> Enter Ambari Admin login: admin
> Enter Ambari Admin password: 
> Syncing all...ERROR: Exiting with exit code 1. 
> REASON: Caught exception running LDAP sync. Unprocessed Continuation Reference(s); nested exception is javax.naming.PartialResultException: Unprocessed Continuation Reference(s); remaining name 'dc=hortonworks,dc=local'
> {noformat}


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)