You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "David McGinnis (JIRA)" <ji...@apache.org> on 2019/04/03 14:57:00 UTC

[jira] [Commented] (HIVE-19183) Confluence Documentation for LDAP Config has unfortunate bug

    [ https://issues.apache.org/jira/browse/HIVE-19183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16808804#comment-16808804 ] 

David McGinnis commented on HIVE-19183:
---------------------------------------

[~madorb]: I'm confused what the issue is here. Here is the current property in the sample configuration you referred to:
{code:java}
hive.server2.authentication.ldap.groupClassKey
{code}
I checked in the source code, and this is the correct configuration key. There hasn't been a change to this page since 2016, so I'm guessing you were seeing the same text I am now. Additionally, your description appears to be off, since you have the same value mentioned twice, instead of one of them using server2. Can you clarify what your concern is here?

> Confluence Documentation for LDAP Config has unfortunate bug
> ------------------------------------------------------------
>
>                 Key: HIVE-19183
>                 URL: https://issues.apache.org/jira/browse/HIVE-19183
>             Project: Hive
>          Issue Type: Bug
>          Components: Documentation
>            Reporter: Ben M
>            Priority: Minor
>
> Not sure how else to notify of this, apparently can't add comments (SAD!) or edit confluence.
>  
> Please see: [https://cwiki.apache.org/confluence/display/Hive/User+and+Group+Filter+Support+with+LDAP+Atn+Provider+in+HiveServer2]
> Note that configuration property defined as: {{hive.server.authentication.ldap.groupClassKey}} SHOULD be
> {{hive.server.authentication.ldap.groupClassKey}} (note {{server}} vs. {{server2}})
> sadly spent a few hours today trying to suss out why my config wasn't working until i realized that my overcaution and copying the exact key from the docs was the root cause :)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)