Mailing-List: contact ambari-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ambari-user@incubator.apache.org
Received-SPF: pass (athena.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
From: Artem Ervits <are9004@nyp.org>
To: "ambari-user@incubator.apache.org" <ambari-user@incubator.apache.org>
Subject: RE: LDAP authentication
Thread-Topic: LDAP authentication
Thread-Index: Ac7KssYOUqbSznSyRtePVl89KdBU4QAInSEAAAfsTGD//8aIgIAAPCUw
Date: Wed, 16 Oct 2013 21:57:48 +0000
Message-ID: 
 <99DD75DC8938B743BBBC2CA54F7224A70E5267E2@NYSGMBXB06.a.wcmc-ad.net>
References: 
 <99DD75DC8938B743BBBC2CA54F7224A70E526691@NYSGMBXB06.a.wcmc-ad.net>
 <CALF7aMRHeoSj-2vO0JFRO+X9sb_VEv1UnQ0k0Z9ZreS3A=tePA@mail.gmail.com>
 <99DD75DC8938B743BBBC2CA54F7224A70E526732@NYSGMBXB06.a.wcmc-ad.net>
 <E82D9AC8-20AC-456B-84FB-FA9E0676FAC8@hortonworks.com>
In-Reply-To: <E82D9AC8-20AC-456B-84FB-FA9E0676FAC8@hortonworks.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

It does say it is ldaps:// so I setup a truststore. Also, I spoke to our L=
DAP guy, he says I need to tell Ambari to trust a local CA. How do I provi=
de a local CA to Ambari?=20

Thanks

-----Original Message-----
From: Mahadev Konar [mailto:mahadev@hortonworks.com]=20
Sent: Wednesday, October 16, 2013 5:29 PM
To: ambari-user@incubator.apache.org
Subject: Re: LDAP authentication

All you need to do post that is login via an ldap user. If a ldap user has=
 already logged in you will see that user in the admin tab. As of now we d=
o not get list of all the users in ldap on that page. Only shows up once a=
 ldap user logs in.

ALso, trustsore no is ok unless you are using a ldaps which need a trustst=
ore for verification.

mahadev

On Oct 16, 2013, at 2:23 PM, Artem Ervits <are9004@nyp.org> wrote:

> That's really convenient, didn't see that option before and didn't see=20=

> documentation for it either. So I followed the questions and it picked=20=

> up all of my answers from the manual configuration. One additional=20
> question=20was to setup a custom truststore, to which I replied no.=20
> Other than that, in Ambari UI do I need to add a user which is in LDAP=20=

> in order to authenticate? I only see an option to add local users. I=20
> am using Ambari 1.2.5
>=20
> Thanks
>=20
> -----Original Message-----
> From: Mahadev Konar [mailto:mahadev@hortonworks.com]
> Sent: Wednesday, October 16, 2013 5:07 PM
> To: ambari-user@incubator.apache.org
> Subject: Re: LDAP authentication
>=20
> Artem,
> You might want to use ambari-server setup-ldap to help you go through th=
e ldap setup. That way you wont miss any properties in your ldap setup.
>=20
> thanks
> mahadev
> Mahadev Konar
> Hortonworks Inc.
> http://hortonworks.com/
>=20
>=20
> On Wed, Oct 16, 2013 at 2:02 PM, Artem Ervits <are9004@nyp.org> wrote:
>> Hello all,
>>=20
>>=20
>>=20
>> I'm trying to configure Ambari with LDAP and I'm a bit stuck.
>>=20
>>=20
>>=20
>> I filled out all of the properties in the installation guide,=20
>> however, I am not able to authenticate with Ambari. I see the following=
 in the logs:
>>=20
>>=20
>>=20
>> INFO AmbariLocalUserDetailsService:67 - user not found
>>=20
>> INFO AmbariLdapAuthenticationProvider:128 - Reloading properties
>>=20
>> INFO AmbariLdapAuthenticationProvider:78 - LDAP Properties changed -=20=

>> rebuilding Context
>>=20
>> INFO AbstractContextSource:330 - Property 'userDn' not set -=20
>> anonymous context will be used for read-write operations
>>=20
>> INFO FilterBasedLdapUserSearch:89 - SearchBase not set. Searches will=20=

>> be performed from the root: ou=3DIS,o=3Dnyp.org
>>=20
>>=20
>>=20
>> Should I add more detail to the Ambari properties file?
>>=20
>>=20
>>=20
>> Thanks.
>>=20
>>=20
>>=20
>> Artem Ervits
>>=20
>> New York Presbyterian Hospital
>>=20
>>=20
>>=20
>>=20
>> This electronic message is intended to be for the use only of the=20
>> named recipient, and may contain information that is confidential or pr=
ivileged.
>> If you are not the intended recipient, you are hereby notified that=20
>> any disclosure, copying, distribution or use of the contents of this=20=

>> message is strictly prohibited. If you have received this message in=20=

>> error or are not the named recipient, please notify us immediately by=20=

>> contacting the sender at the electronic mail address noted above, and=20=

>> delete and destroy all copies of this message. Thank you.
>=20
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity=
 to which it is addressed and may contain information that is confidential=
, privileged and exempt from disclosure under applicable law. If the reade=
r of this message is not the intended recipient, you are hereby notified t=
hat any printing, copying, dissemination, distribution, disclosure or forw=
arding of this communication is strictly prohibited. If you have received =
this communication in error, please contact the sender immediately and del=
ete it from your system. Thank You.
>=20
> This electronic message is intended to be for the use only of the named =
recipient, and may contain information that is confidential or privileged.=
  If you are not the intended recipient, you are hereby notified that any =
disclosure, copying, distribution or use of the contents of this message i=
s strictly prohibited.  If you have received this message in error or are =
not the named recipient, please notify us immediately by contacting the se=
nder at the electronic mail address noted above, and delete and destroy al=
l copies of this message.  Thank you.


--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity t=
o which it is addressed and may contain information that is confidential, =
privileged and exempt from disclosure under applicable law. If the reader =
of this message is not the intended recipient, you are hereby notified tha=
t any printing, copying, dissemination, distribution, disclosure or forwar=
ding of this communication is strictly prohibited. If you have received th=
is communication in error, please contact the sender immediately and delet=
e it from your system. Thank You.

This electronic message is intended to be for the use only of the named re=
cipient, and may=20contain information that is confidential or privileged.=
  If you are not the intended recipient, you are hereby notified that any =
disclosure, copying, distribution or use of the contents of this message i=
s strictly prohibited.  If you have received this message in error or are =
not the named recipient, please notify us immediately by contacting the se=
nder at the electronic mail address noted above, and delete and destroy al=
l copies of this message.  Thank you.