[
https://issues.apache.org/jira/browse/ARTEMIS-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850725#comment-15850725
]
Ruben Cala commented on ARTEMIS-939:
------------------------------------
I did not modify it at all from the default login.config that's created for a
new instance. It only has:
/* standard header ...
*/
activemq {
org.apache.activemq.artemis.spi.core.security.jaas.PropertiesLogModule
required
debug=false
org.apache.activemq.jaas.properties.user="artemis-users.properties",
org.apache.activemq.jaas.properties.role="artemis-roles.properties";
> User list not updated on the broker dynamically
> -----------------------------------------------
>
> Key: ARTEMIS-939
> URL: https://issues.apache.org/jira/browse/ARTEMIS-939
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 1.5.2
> Environment: Redhat Linux 6
> Reporter: Ruben Cala
> Assignee: Justin Bertram
> Fix For: 2.0.0, 1.5.x
>
>
> The new artemis user command option updates the artemis-users.properties and
> artemis-roles.properties files, but the broker does not pick up the changes
> without being recycled. Dynamically updating the user list on the broker
> seems like a sensible feature, especially when considering that configuration
> reload (of broker.xml) is now supported. Not sure if this is a bug or just
> not implemented. (FYI I tried modifying the user list, then forcing a
> configuration reload by doing a touch on broker.xml, but the new user list
> did not apply to the broker.)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
