: Set your authorizer logs to DEBUG in your broker's log4j.properties to see exactly which user is being denied.
: Before a message is sent, the client checks if the user has Write permissions for that topic. Authorisation Error
While I can't build the code directly into your app, I can suggest a high-level feature design for a "Smart Authorization Guard" that would help your system handle these errors automatically. Feature Proposal: Smart Authorization Guard : Set your authorizer logs to DEBUG in your broker's log4j
: 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 Feature Proposal: Smart Authorization Guard : If a
If you are currently facing this error, you can resolve it by following these steps:
: 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) .
It sounds like you're looking for a new to handle Authorisation Errors when a Producer tries to send data to a Kafka topic.
Mylf Discount! Only $9.95/month! Don't miss this exclusive offer!