[jira] [Created] (ATLAS-1546) Hive hook should choose appropriate JAAS config if host uses kerberos ticket-cache

["Madhan Neethiraj (JIRA)" <ji...@apache.org>]

Madhan Neethiraj created ATLAS-1546:
---------------------------------------

             Summary: Hive hook should choose appropriate JAAS config if host uses kerberos ticket-cache
                 Key: ATLAS-1546
                 URL: https://issues.apache.org/jira/browse/ATLAS-1546
             Project: Atlas
          Issue Type: Improvement
          Components: atlas-intg
    Affects Versions: 0.7-incubating, 0.8-incubating
            Reporter: Madhan Neethiraj


In a kerberized environment, Atlas hook uses JAAS configuration section named "KakfaClient" to authenticate with Kafka broker. In a typical Hive deployment this configuration section is set to use the keytab and principal of HiveServer2 process. The hook running in HiveCLI might fail to authenticate with Kafka if the user can't read the configured keytab.

Given that HiveCLI users would have performed kinit, the hook in HiveCLI should use the ticket-cache generated by kinit. When ticket cache is not available (for example in HiveServer2), the hook should use the configuration provided in KafkaClient JAAS section.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)