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

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.7-incubating, 0.8-incubating
• Fix Version/s: 0.8-incubating
• Component/s: atlas-intg
• Assignee: Nixon Rodrigues
• Reporter: Madhan Neethiraj
• Created: 10/Feb/17 07:41
• Updated: 07/Mar/17 20:50
• Resolved: 14/Feb/17 00:17

Description

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.

Issue Links

• duplicates: AMBARI-19790 HiveCLI and AtlasHook do not work correctly
• links to: Review request