Hi, you should not use your own MBean server but prefer the Karaf provided one.
It should work smoothly. Whyt not using the default Karaf one ? Regards JB On 01/12/2017 03:30 PM, rsteppac2 wrote:
I am trying to set up Karaf in a Docker container for remote JMX access. With authentication disabled those properties allow me to connect remotely via jconsole: -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.rmi.port=1097 -Dcom.sun.management.jmxremote.port=1098 -Dcom.sun.management.jmxremote.authenticate=false -Djava.rmi.server.hostname=$HOST_HOSTNAME With remote authentication enforced I can managed to use Karaf's JAAS setup for authenticating JMX access: -Dcom.sun.management.jmxremote.login.config=karaf -Djava.security.auth.login.config=$KARAF_HOME/etc/users.properties However, on successful authentication the VM looks at its jmxremote.access file for authorization and of course that file does not contain my user. How can I get the VM to use Karafs ACL mechanisms for remote JMX authorization instead of using a plain property file like the jmxremote.access file? Thanks! -- View this message in context: http://karaf.922171.n3.nabble.com/How-to-authorize-remote-JMX-access-tp4049177.html Sent from the Karaf - User mailing list archive at Nabble.com.
-- Jean-Baptiste Onofré [email protected] http://blog.nanthrax.net Talend - http://www.talend.com
