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:
- 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).
- Make code changes to enable Kudu authentication