[
https://issues.apache.org/jira/browse/HIVE-13401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chaoyu Tang updated HIVE-13401:
-------------------------------
Description: When HS2 is running in kerberos cluster but with other Sasl
authentication (e.g. LDAP) enabled, it fails in kerberos/delegation token
authentication. It is because the HS2 server uses the TSetIpAddressProcess when
other authentication is enabled. (was: When HS2 is running in kerberos
cluster but with other Sasl authentication (e.g. LDAP) enabled, it fails in
delegation token authentication. It is because the HS2 server uses the
TSetIpAddressProcess when other authentication is enabled. )
Summary: Kerberized HS2 with LDAP auth enabled fails
kerberos/delegation token authentication (was: Kerberized HS2 with LDAP auth
enabled fails the delegation token authentication )
> Kerberized HS2 with LDAP auth enabled fails kerberos/delegation token
> authentication
> ------------------------------------------------------------------------------------
>
> Key: HIVE-13401
> URL: https://issues.apache.org/jira/browse/HIVE-13401
> Project: Hive
> Issue Type: Bug
> Components: Authentication
> Reporter: Chaoyu Tang
> Assignee: Chaoyu Tang
> Attachments: HIVE-13401.patch
>
>
> When HS2 is running in kerberos cluster but with other Sasl authentication
> (e.g. LDAP) enabled, it fails in kerberos/delegation token authentication. It
> is because the HS2 server uses the TSetIpAddressProcess when other
> authentication is enabled.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
