[IMPALA-4460] Investigate and support Kudu basic authentication

• Type: New Feature
• Status: Resolved
• Priority: Critical
• Resolution: Duplicate
• Affects Version/s: Impala 2.8.0
• Fix Version/s: Impala 2.9.0
• Component/s: Security
• Labels: kudu security
• Target Version: Impala 3.0
• Assignee: Unassigned
• Reporter: Matthew Jacobs
• Created: 10/Nov/16 00:16
• Updated: 23/Feb/17 17:26
• Resolved: 23/Feb/17 17:26

Description

Kudu is adding basic authentication via kerberos (which is the first stage of a much broader pipeline of security features). It sounds like the Kudu client will use kerberos/sasl internally, possibly requiring Impala to make a call on the Kudu client, but we don't have the details yet.

Once we have details about what changes will occur, we need to:

1. Evaluate the impact for Impala. This includes considering the impact of the kudu client interacting with kerberos/sasl in the Impala process (e.g. will this interact with / break Impala's existing kerberos mechanisms).
2. Make code changes to enable Kudu authentication
3. Testing