[Solved] A Kafka client config uses:security.protocol=SASL_PLAINTEXT sasl.mechanism=GSSAPIThe client fails to authenticate. What could be a likely cause? | Kafka

Kafka - Security

A Kafka client config uses:

security.protocol=SASL_PLAINTEXT
sasl.mechanism=GSSAPI

The client fails to authenticate. What could be a likely cause?

Asecurity.protocol should be SSL, not SASL_PLAINTEXT

BMissing Kerberos ticket or incorrect JAAS config

Csasl.mechanism GSSAPI is unsupported

DPLAINTEXT disables all authentication

Step-by-Step Solution

Solution:

Step 1: Understand GSSAPI mechanism
GSSAPI uses Kerberos for authentication, requiring valid tickets and JAAS config.
Step 2: Analyze failure reasons
Missing Kerberos ticket or misconfigured JAAS causes authentication failure; SASL_PLAINTEXT allows auth without encryption.
Final Answer:
Missing Kerberos ticket or incorrect JAAS config -> Option B
Quick Check:
GSSAPI needs Kerberos ticket and JAAS config [OK]

Quick Trick: GSSAPI requires Kerberos ticket and JAAS config [OK]

Common Mistakes:

Master "Security" in Kafka

9 interactive learning modes - each teaches the same concept differently

More Kafka Quizzes

A Kafka client config uses: