Hi,

Please refer below article to enable JMX authentication in JVM

https://db.apache.org/derby/docs/10.9/adminguide/radminjmxenablepwd.html

Hello Mark,

If you want to enable JMX with no authentication have a look at below article

https://db.apache.org/derby/docs/10.10/adminguide/radminjmxenablenoauth.html

Thanks,

Arun

Thanks for the replies.

Arun - I am trying to get SMA to work with authentication.  It works just fine if authentication is set to false.

Sudhakar - I am aware of both the access.xml and password.xml file, but have not been able to get it to work with the SMA login.  Do you have an example?  Does it need to be coordinated with the SMA related entries (PegaDiagnosticUser) in the tomcat-users.xml file that are needed for SMA?

Thanks.

Thanks Sudhakar - please let me know what you find.   SMA uses jmxremote to connect to the node, so the two (SMA and jmxremote) would appear to be related.   If I set jmxremote.authenticate=false in setenv.sh, SMA will connect just fine even if you put in totally incorrect credentials into the SMA id/password fields (using "always prompt for credentials" in the SMA node definition).  If jmxremote.authenticate=true (a requirement for us), then I can't get it to work at all.

Thanks

Hi Sudhakar - I have found where the issue may be (haven't gotten a working solution yet).  It appears that our middleware team has Tomcat integrated with LDAP.   If I remove the following two entries:  -Dcom.sun.management.jmxremote.login.config=Tomcat -Djava.security.auth.login.config=$CATALINA_HOME/login.config   (indicates ldap)

and instead specify a local jmxremote.password file instead, I can get SMA to work fine with ids that I put in the jmxremote.access and jmxremote.password files.

Now I just need to figure out how to get it to work with ldap...