You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Philip Nee (Jira)" <ji...@apache.org> on 2023/11/10 05:30:00 UTC
[jira] [Updated] (KAFKA-10840) Need way to catch auth issues in poll method of Java Kafka client
[ https://issues.apache.org/jira/browse/KAFKA-10840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Philip Nee updated KAFKA-10840:
-------------------------------
Labels: authentication client (was: )
> Need way to catch auth issues in poll method of Java Kafka client
> -----------------------------------------------------------------
>
> Key: KAFKA-10840
> URL: https://issues.apache.org/jira/browse/KAFKA-10840
> Project: Kafka
> Issue Type: Improvement
> Reporter: Devin G. Bost
> Priority: Blocker
> Labels: authentication, client
>
> We recently implemented SSL authentication at our company, and when certs expire, the Kafka client poll method silently fails without throwing any kind of exception. This is a problem because the data flow could stop at any time (due to certificate expiration) without us being able to handle it. The auth issue shows up in Kafka broker logs, but we don't see any indication on the client-side that there was an auth issue. As a consequence, the auth failure happens 10 times a second forever.
> We need a way to know on the client-side if an auth issue is blocking the connection to Kafka so we can handle the exception and refresh the certs (keystore/truststore) when the certs expire.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)