Authorisation Error Apr 2026

: Instead of a generic error, the feature would log the specific Principal (user) and Resource (topic) that failed, making it much faster for your DevOps team to fix the ACLs (Access Control Lists) .

The most common version of this is the TOPIC_AUTHORIZATION_FAILED error, which usually happens because a service account or user doesn't have the right permissions to write to a specific topic. Authorisation Error

: Set your authorizer logs to DEBUG in your broker's log4j.properties to see exactly which user is being denied. : Instead of a generic error, the feature

: Ensure your Service Account has the WRITE operation allowed on the Topic resource. : Ensure your Service Account has the WRITE

It sounds like you're looking for a new to handle Authorisation Errors when a Producer tries to send data to a Kafka topic.

[Error while producing messages with authorization enabled] #3011

: If a producer is unauthorized to write to a mission-critical topic, the feature could temporarily route those messages to a safe "quarantine" topic or local storage so no data is lost during the downtime. How to Implement This Today