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`:
```
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
