atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jayendra Parab <>
Subject Re: Review Request 72527: Refactoring Kafka JAAS Configuration
Date Tue, 19 May 2020 11:25:24 GMT

This is an automatically generated e-mail. To reply, visit:

(Updated May 19, 2020, 11:25 a.m.)

Review request for atlas, Madhan Neethiraj, Nixon Rodrigues, and Sarath Subramanian.

Bugs: ATLAS-3779

Repository: atlas


The JAAS config set through InMemoryJAASConfiguration overwrites user supplied JAAS configuration
which might be required to connect to user's Kakfa instead of Atlas's Kafka and might have
different credentials

To resolve this we should make use of Kafka's dynamic JAAS configuration mechanism wherein
you can set the Kafka JAAS config using sasl.jaas.config property. (

In this patch, we are picking up the atlas.jaas.* properties and setting the sasl.jaas.config
property. Since the JAAS configuration is specific only to Kafka, the JAAS property initialization
is done while instantiating the KafkaNotification object. Also, since we are using sasl.jaas.config
property to set the configuration it's not conflicting with any other JAAS configuration.

To keep the code backward compatible for client application which make use of ticketBased-KafkaClient
configuration , we are still making use of the earlier mechanism i.e. with the use of UserGroupInformation.isLoginTicketBased()
and UserGroupInformation.isLoginKeytabBased() to set the configuration.


  intg/src/main/java/org/apache/atlas/ 3ba50612e 
  notification/src/main/java/org/apache/atlas/hook/ cc6546be8 
  notification/src/main/java/org/apache/atlas/kafka/ 11a29b9e0 



With these changes, tried creating table using CTAS query in Hive. The entities corresponding
to the table was updated properly in Atlas server


Jayendra Parab

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message