ACL expiration about emqx-auth-http HOT 6 OPEN

hello, any updates on this?

from emqx-auth-http.

Hi, guys. Thanks for your feedback. I'll implement this feature at v3.2.0

A workaround before v3.2.0 is changing the acl_cache_ttl of emqx.conf:

## The time after which an ACL cache entry will be deleted
##
## Value: Duration
## Default: 1 minute
acl_cache_ttl = 1m

from emqx-auth-http.

hello @HJianBo , how to make the cache works? I just tested and find that even when I have the following settings in my emqx.conf:

## Whether to enable ACL cache.
## If enabled, ACLs roles for each client will be cached in the memory
enable_acl_cache = on
## The maximum count of ACL entries can be cached for a client.
acl_cache_max_size = 32
## The time after which an ACL cache entry will be deleted
acl_cache_ttl = 1m
bridge.aws.queue.mem_cache = on

when I use tcpdump to see the traffic, I can still see every time when I publish a message, it's sending requests -> /emqx/auth, /emqx/superuser, /emqx/acl.

what I did:

mosquitto_sub -t test -u jiangch1 -P jiangch1

and I use this to publish:

mosquitto_pub -t test -u jiangch1 -P jiangch1 -m test -k 60

Any ideas to make it works?

from emqx-auth-http.

@HJianBo sorry I find that when I use mqtt.js it's ok, it will just send the auth request the fist time. Cool!

One question, can I know when [email protected] will be release?

from emqx-auth-http.

Maybe two weeks later. We enhance a numbers of new features, so I can't give a explicit deadline.

If it released I'll mention it here

from emqx-auth-http.

@HJianBo great thanks!

from emqx-auth-http.