Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
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.
Attachments
Attachments
Issue Links
- breaks
-
HIVE-13590 Kerberized HS2 with LDAP auth enabled fails in multi-domain LDAP case
- Closed
- is related to
-
HIVE-10115 HS2 running on a Kerberized cluster should offer Kerberos(GSSAPI) and Delegation token(DIGEST) when alternate authentication is enabled
- Closed