Hi DK-
Yes, you need to update the bin/activemq startup script to do two things:
1. List a classpath, instead of just one jar. It must include the
bin/activemq.jar, lib/activemq-jaas.jar and lib/slf4j-api.jar.
2. Add the name of the ‘Main’ class to run on startup
For example, take a classpath
Hi Matt,
I have provided a login.config as 'activemq' but still java is not
considering this. Is this settings are specific to any perticular ActiveMQ
version?
We are currently using 5.16.1 with jdk 8.
Thank You.
Regards,
DK
On Wed, 3 May 2023, 20:44 Matt Pavlovich, wrote:
> Hello DK-
>
> A
Hello DK-
ActiveMQ uses the standard Java JDK parameters for enabling JMX.
The JMX flag for using the ‘activemq' JAAS login context name is:
-Dcom.sun.management.jmxremote.login.config=activemq
Modifications to ActiveMQ’s startup is needed to add a classpath used by your
custom JAAS module —
Hi Matt,
Thank you for your response. Currently I
have created own custom login module and updated login config with the
module. Provided that login config in jvm parameter also provided the
module name which I want to use. Also updated the activemq.xml file to
include jaasplugin. Still my custom
Hello DK-
Yes, reconfiguring JMX to use JAAS would be the approach to use encrypted
passwords.
I plan on converting the Apache distribution to use JAAS for JMX by default in
an upcoming release. For now, you’ll need to convert it yourself.
Related JIRA:
https://issues.apache.org/jira/browse/A
