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
: Make sure your JAAS config (username/password/SSL) is correct, as authorization can't happen if the broker doesn't know who you are. Authorisation Error
: 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) . While I can't build the code directly into
[Error while producing messages with authorization enabled] #3011 Authorisation Error