hachikuji commented on code in PR #12673:
URL: https://github.com/apache/kafka/pull/12673#discussion_r977019044
##########
docs/security.html:
##########
@@ -1136,13 +1136,29 @@ <h3 class="anchor-heading"><a id="security_sasl"
class="anchor-link"></a><a href
</ol>
<h3 class="anchor-heading"><a id="security_authz"
class="anchor-link"></a><a href="#security_authz">7.4 Authorization and
ACLs</a></h3>
- Kafka ships with a pluggable Authorizer and an out-of-box authorizer
implementation that uses zookeeper to store all the acls. The Authorizer is
configured by setting <tt>authorizer.class.name</tt> in server.properties. To
enable the out of the box implementation use:
+ Kafka ships with a pluggable authorization framework, which is configured
by setting <tt>authorizer.class.name</tt> in server.properties. Configured
implementations must extend
<code>org.apache.kafka.server.authorizer.Authorizer</code>. Kafka provides
default implementations which store ACLs in the cluster metadata (either
Zookeeper or the KRaft metadata log).
Review Comment:
We do, but it does seem a little odd. I tried to reword it without the
explicit mention of `server.properties`.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: jira-unsubscr...@kafka.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
