The difference is that you need to pass in to LDAP username and password.
2013/12/20 Mikhail Antonov <olorinb...@gmail.com> > Could you elaborate what do you mean by "authenticate against _anonymous_ > LDAP server"? > > > 2013/12/20 Ron Echeverri <recheve...@maprtech.com> > >> I'll collect this, but to confirm, if hive is configured to authenticate >> against an anonymous LDAP server, and that works, the configuration should >> also work against a binding-required LDAP server? >> >> >> On Fri, Dec 20, 2013 at 2:46 PM, Mikhail Antonov <olorinb...@gmail.com>wrote: >> >>> Would help if you show logs/errors from the failing binding. >>> >>> - do you use schema, when Hiveserver2 itself authenticates to Namenode >>> via kerberos, and end users authenticate via ldap with proxied kerberos >>> tickets? >>> - How do you pass in username/password, could you post here relevant >>> piece of hive-site.xml?-- >>> - Is the connection to LDAP over SSL? Can you successfully bind from >>> the same host as runs HS2 from apache directory studio or other LDAP tool? >>> >>> Mikhail >>> >>> >>> 2013/12/20 Ron Echeverri <recheve...@maprtech.com> >>> >>>> I have a customer whose hiveserver2 settings work fine authenticating >>>> against one LDAP server where anonymous requests are allowed, but failing >>>> against another LDAP server where binding is mandatory. Are there further >>>> configurations for hiveserver to work against a bind-only LDAP server? Is >>>> Hiveserver2 agnostic about it and the problem lies on the LDAP side? Any >>>> guidance would be appreciated. >>>> >>>> thanks >>>> rone >>>> >>> >>> >>> >>> -- >>> Thanks, >>> Michael Antonov >>> >> >> > > > -- > Thanks, > Michael Antonov > -- Thanks, Michael Antonov
