- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Trouble adding custom LoginModule to consumeKafkaRecord_2_6 Apache Nifi Flow
- Labels:
-
Apache Kafka
-
Apache NiFi
-
Kerberos
-
Security
Created on
‎11-03-2021
07:28 PM
- last edited on
‎11-04-2021
05:46 AM
by
cjervis
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am using the ConsumeKafkaRecord_2_6 processor to consume from kafka. I am trying to use a custom LoginModule. I have both a custom LoginModule and a custom CallbackHandler. I put my two classes in a jar then loaded the jar on the Nifi system. When the processor starts, I get this error:
Caused by: javax.security.auth.login.LoginException: unable to find LoginModule class: com.eek.my.auth.krb.SauKrbLoginModuleWrapper. I am not sure how to add the jar so that the processor will find my classes. The dynamic property I am adding to reference the custom class is sasl.jaas.config. So the value of that looks like this: sasl.jaas.config=com.eek.my.auth.krb.SauKrbLoginModuleWrapper required krbProvider=com.sun.security.auth.module.Krb5LoginModule;
Created ‎11-05-2021 06:09 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
After adding the jar to the consumeKafkaRecord NAR and bouncing the servers, I am no longer receiving the error. Now I am able to authenticate to Kafka using the GSSAPI SASL mechanism.
Created ‎11-04-2021 07:43 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am requesting now the nar for the ConsumeKafkaRecord be updated to include my new jar. Not sure if that is the only way for the processor to pick it up.
Created ‎11-05-2021 06:09 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
After adding the jar to the consumeKafkaRecord NAR and bouncing the servers, I am no longer receiving the error. Now I am able to authenticate to Kafka using the GSSAPI SASL mechanism.
