acl support about moquette HOT 9 CLOSED

Are there any plans to support this?

from moquette.

Yes, it's on the stack of todos. Before I've to introduce the concept of plugins.

from moquette.

Implemented ACL with same synthax used in Mosquitto.

from moquette.

Hey Adnsel, I am having a problem with the access control list in Moquttee, It seems that it is working so strange, I have posted a question on stack overflow, here it is http://stackoverflow.com/questions/31511811/moquette-users-have-privilege-different-than-what-is-written-in-the-access-contr
could you check please

from moquette.

Hi William,
I've seen it, I'll check it on the first free slot during night development.

Andrea

On Mon, Jul 20, 2015 at 10:28 AM, William Kinaan [email protected]
wrote:

Hey Adnsel, I am having a problem with the access control list in
Moquttee, It seems that it is working so strange, I have posted a question
on stack overflow, here it is
http://stackoverflow.com/questions/31511811/moquette-users-have-privilege-different-than-what-is-written-in-the-access-contr
could you check please

—
Reply to this email directly or view it on GitHub
https://github.com/andsel/moquette/issues/10#issuecomment-122812085.

from moquette.

Answered, probably you refer or touch the bad file, If you can't fix please refer to mailining list or github issues, posting your moquette.conf, acl.conf and password.conf

Andrea

from moquette.

Hi Andsel,
I highly doubt that there is a bug in the authorization part of my version, because look at the code for receiving a subscribe event

@MQTTMessage(message = SubscribeMessage.class)
void processSubscribe(ServerChannel session, SubscribeMessage msg) {
String clientID = (String) session
.getAttribute(NettyChannel.ATTR_KEY_CLIENTID);
boolean cleanSession = (Boolean) session
.getAttribute(NettyChannel.ATTR_KEY_CLEANSESSION);
LOG.debug("SUBSCRIBE client <{}> packetID {}", clientID,
msg.getMessageID());

    // ack the client
    SubAckMessage ackMessage = new SubAckMessage();
    ackMessage.setMessageID(msg.getMessageID());

    for (SubscribeMessage.Couple req : msg.subscriptions()) {
        AbstractMessage.QOSType qos = AbstractMessage.QOSType.values()[req
                .getQos()];
        Subscription newSubscription = new Subscription(clientID,
                req.getTopicFilter(), qos, cleanSession);
        boolean valid = subscribeSingleTopic(newSubscription,
                req.getTopicFilter());
        ackMessage.addType(valid ? qos : AbstractMessage.QOSType.FAILURE);
    }

There is no call for the can.read function.

That is the problem, I am even developing a plugin for authorization, and the authorization on publishing is working perfectly, but the authorization on subscription is not working.

May you check please?

Many thanks,

from moquette.

Hi man,

So sorry, it is working perfectly :)

And my plugin for authorization is working now

Appreciate it

from moquette.

Ok, great!

from moquette.