[Solved] In this Kafka client config snippet:props.put("security.protocol", "SASL_SSL"); props.put("sasl.mechanism", "GSSAPI"); props.put("sasl.jaas.config", "com.sun.... What is the most probable cause? | Kafka

Kafka - Security

In this Kafka client config snippet:

props.put("security.protocol", "SASL_SSL");
props.put("sasl.mechanism", "GSSAPI");
props.put("sasl.jaas.config", "com.sun.security.auth.module.Krb5LoginModule required useKeyTab=true keyTab=\"/etc/kafka/kafka.keytab\" principal=\"kafka/host@EXAMPLE.COM\";");

The client fails with a login error. What is the most probable cause?

AIncorrect keytab file path or permissions

BWrong sasl.mechanism value for Kerberos

CMissing security.protocol property

DUsing SASL_PLAINTEXT instead of SASL_SSL

Step-by-Step Solution

Solution:

Step 1: Understand Kerberos JAAS config
Kerberos login requires correct keytab file path and read permissions.
Step 2: Identify common login error cause
Login errors often happen if keytab file is missing or inaccessible due to permissions.
Final Answer:
Incorrect keytab file path or permissions -> Option A
Quick Check:
Kerberos login needs valid keytab file accessible [OK]

Quick Trick: Check keytab file path and permissions for Kerberos login [OK]

Common Mistakes:

Using wrong sasl.mechanism
Omitting security.protocol
Confusing SASL_SSL with SASL_PLAINTEXT
Ignoring file permission issues

Master "Security" in Kafka

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

More Kafka Quizzes

In this Kafka client config snippet:

Step 1: Understand Kerberos JAAS config

Step 2: Identify common login error cause

Final Answer:

Quick Check:

Want More Practice?