Security Configuration

WSO2 Message Broker Uses Apache ZooKeeper to handle clustering such as listen to, notify and synchronize cluster across messages. The idea is to all clients connecting to zookeeper should be authenticated so that instances not belonging to the cluster cannot mess with the cluster across messages that are shared between the authenticated ones. 

If exist, edit the file at <MB_HOME>/repository/conf/security/jaas.conf file. Otherwise you must create it.

Add following contents to the file.

Server {
       org.apache.zookeeper.server.auth.DigestLoginModule required
       user_super="admin"
       user_admin="admin";
};
Client {
       org.apache.zookeeper.server.auth.DigestLoginModule required
       username="admin"
       password="admin";
};

Note that this is only an example configuration. You can use any username and password as appropriate.

Note that the passwords in the above are in plain text, so the JAAS configuration file should not be readable by anyone other than the Zookeeper server process user.

If you wish not to use SASL authentication remove "Client" part in above configuration. If ZooKeeper server allows you may continue without SASL.