hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David McGinnis (JIRA)" <>
Subject [jira] [Commented] (HIVE-21009) LDAP - Specify binddn for ldap-search
Date Wed, 06 Feb 2019 17:54:00 GMT


David McGinnis commented on HIVE-21009:

[~prasanth_j]: I looked in that pom, and it should be covered by the line which excludes anything
inside of a resources folder (which the jceks file is).

I believe we are seeing that error due to a commit a few days ago of []
which does not have a license at the top of the file. My understanding of the desired process
is that you shouldn't make changes outside of the bug you are working on (and simple cleanup
of the code around it), so I'm not sure I'm supposed to add the license to the file as part
of this change, as part of a separate change, or just ignore it until someone else fixes it.
Feel free to give me guidance on this.

> LDAP - Specify binddn for ldap-search
> -------------------------------------
>                 Key: HIVE-21009
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: HiveServer2
>    Affects Versions: 2.1.0, 2.1.1, 2.2.0, 2.3.0, 2.3.1, 2.3.2
>            Reporter: Thomas Uhren
>            Assignee: David McGinnis
>            Priority: Major
>              Labels: features, newbie, security
>         Attachments: HIVE-21009.01.patch, HIVE-21009.02.patch, HIVE-21009.03.patch, HIVE-21009.04.patch,
HIVE-21009.05.patch, HIVE-21009.06.patch, HIVE-21009.07.patch, HIVE-21009.patch
> When user accounts cannot do an LDAP search, there is currently no way of specifying
a custom binddn to use for the ldap-search.
> So I'm missing something like that:
> {code}
> hive.server2.authentication.ldap.bindn=cn=ldapuser,ou=user,dc=example
> hive.server2.authentication.ldap.bindnpw=password
> {code}

This message was sent by Atlassian JIRA

View raw message