[IMPALA-13118] Removing explicit ascii encoding of kerberos_host_fqdn when -b/--kerberos_host_fqdn is used

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: Impala 4.4.0
• Component/s: Clients
• Labels: Python3 impala-shell
• Epic Color: ghx-label-6
• Assignee: Vincent Tran
• Reporter: Vincent Tran
• Created: 30/May/24 16:15
• Updated: 30/May/24 16:31
• Resolved: 30/May/24 16:31

Description

IMPALA-651 added an explicit encoding for sasl_host to ascii before passing it to sasl_client.setAttr(). This is no longer required after sasl was upgraded to 0.2.1 in IMPALA-9719. This explicit encoding also causes an error in Python 3 when -b is used:

Starting Impala Shell with Kerberos authentication using Python 3.6.8
Using service name 'impala'
SSL is enabled. Impala server certificates will NOT be verified (set --ca_cert to change)
Error connecting: TTransportException, Could not start SASL: b'Error in sasl_client_start (-1) SASL(-1): generic failure: GSSAPI Failure: no serverFQDN'

Issue Links

• duplicates: IMPALA-12552 impala-shell should not call encode on kerberos_host_fqdn in python 3 env
• is related to: IMPALA-9719 Upgrade sasl-0.1.1 to 0.2.1 in Impala/shell/ext-py
• is related to: IMPALA-651 In Kerberized environment Impala-shell -k to start shell prompt and then connect <impalad-hostname> throws exception
• is related to: IMPALA-3343 Impala-shell compatibility with python 3
• is related to: IMPALA-2782 Allow Impala Shell to connect directly to impalad when config with proxy load balancer and kerberos