[
https://issues.apache.org/jira/browse/METRON-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15961115#comment-15961115
]
ASF GitHub Bot commented on METRON-819:
---------------------------------------
Github user nickwallen commented on the issue:
https://github.com/apache/incubator-metron/pull/507
> @mmiklavc Can you try listing and applying acls with the root user
instead of metron?
Ok, sure.
1. As root, I can see the ACLs. But oddly there are none set.
```
[root@node1 ~]# kafka-acls.sh --list --topic yaf --authorizer-properties
zookeeper.connect=node1:2181
Current ACLs for resource `Topic:yaf`:
```
2. Then I set the ACLs again. So this looks pretty good. Now it looks
like they were set.
```
[root@node1 ~]# kafka-acls.sh --authorizer
kafka.security.auth.SimpleAclAuthorizer --authorizer-properties
zookeeper.connect=node1:2181 --add --allow-principal User:metron --group
yaf_parser;
Adding ACLs for resource `Group:yaf_parser`:
User:metron has Allow permission for operations: All from hosts: *
Current ACLs for resource `Group:yaf_parser`:
User:metron has Allow permission for operations: All from hosts: *
```
3. But then if I immediately check them again and they do not exist.
Weird.
```
[root@node1 ~]# kafka-acls.sh --list --topic yaf --authorizer-properties
zookeeper.connect=node1:2181 --authorizer
kafka.security.auth.SimpleAclAuthorizer
Current ACLs for resource `Topic:yaf`:
```
> Document kafka console producer parameter for sensors with kerberos
> -------------------------------------------------------------------
>
> Key: METRON-819
> URL: https://issues.apache.org/jira/browse/METRON-819
> Project: Metron
> Issue Type: Improvement
> Reporter: Michael Miklavcic
> Assignee: Michael Miklavcic
>
> Snort and Yaf use the Kafka console producer. These sensors need an
> additional parameter to work with Kerberos.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
