title: Restrict Topic creation/alteration
body: <p>I've a 3-node unsecured kafka(v0.10.2.1) cluster with topic auto creation and deletion disabled with the following in <code>server.properties</code></p>
  
  <pre><code>auto.create.topics.enable=false
  delete.topic.enable=true
  </code></pre>
  
  <p>Topics are then created/altered on the cluster using <code>bin/kafka-topics.sh</code>. However, it looks like anyone can create topics on the cluster once they know the end points. </p>
  
  <p>Is there a way to lock down topic creation/alteration to specific hosts to prevent abuses?</p>
  
  <hr>
  
  <p><strong>Edit 1</strong>:<br>
  Since ACL was suggested, I tried to restrict topic creation to select hosts using <code>kafka-acls.sh</code>. </p>
  
  <p>I restarted the brokers after adding the following to <code>server.properties</code>, .</p>
  
  <pre><code>authorizer.class.name=kafka.security.auth.SimpleAclAuthorizer                                           
  allow.everyone.if.no.acl.found=true
  </code></pre>
  
  <p>I tried the below to restrict topic creation on localhost. </p>
  
  <pre><code> bin/kafka-acls.sh --authorizer-properties zookeeper.connect=localhost:2181 --add --allow-principal User:* --cluster --operation Create --allow-host 127.0.0.1
  </code></pre>
  
  <p>However, I was still able to create topics from an other host using <code>kafka-topics.sh</code> with the right endpoints.  Is it the case that ACLs can't be used without authentication?</p>
  
  <hr>