Hi ActiveMQ community, I am asking for opinion and buy-in on an idea I have lately before diving into implementation. The idea is a new user management experience in ActiveMQ Classic.
Right now, the way to provision new users on ActiveMQ Classic with default JAAS plugin (and assuming not using LDAP) is by changing a few configuration files and restarting the broker. There are a few drawbacks with the current approach: 1. Knowing which files to change and actually changing them correctly require technical knowledge and needs to be performed by someone who has access to the host servers. 2. It is prone to human error (typo ... etc) that can cause the broker to fail on startup. 3. Any change to users will require a reboot of the broker, which reduces the availability of the broker. Hence I am proposing a new user management experience that has two important improvements: 1. Broker users can be provisioned, removed and modified by an admin user (who may not have technical knowledge or access to the server host) using the web console of the broker. The admin can also use it to modify authorization policy of each user on different destination via intuitive UI. 2. Any change made will kick in real-time without broker restart. Would love to get the community's opinion, potential concern ... etc on the idea before following up with a design / requirement proposal. What do you think? Thanks. Regards, Ken
