You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@kafka.apache.org by Kasper Andersen Storgaard <ka...@trifork.com.INVALID> on 2025/01/07 14:12:01 UTC

Handling Private Methods in AclAuthorizer and Transition to StandardAuthorizer

Hi Kafka Team,


We’re upgrading from Kafka v3.7.1 to v3.9.0 and encountered issues with our custom Kafka Authorizer that extends AclAuthorizer. Starting with Kafka v3.8.0, methods like logAuditMessage and isSuperUser in AclAuthorizer were made private, which breaks our implementation.

1. Is this change intentional, and if so, is there a recommended way to handle logging or superuser checks in custom authorizers?

2. With the move to KRaft, we noticed the StandardAuthorizer is used. Should we transition to this for KRaft environments, and does it provide equivalent functionality for custom logic?


Any guidance would be greatly appreciated!


Best regards,

Kasper