@bonito Hello you noted this in your message: I understand this URL format is different to that suggested in Splunk WAS addon, but this is for a secured WebSphere instance which will not work with those instructions. This URL format should work with a secured instance as long as the correct SSL/SAS properties are set and -Djmx.remote.protocol.provider.pkgs=com.ibm.websphere.management.remote is also set, which I have done with a change to jmx.py. I'm fairly confident it will work if I can get the correct jmxServiceURL passed into the input. I am also attempting to get mbeans from a secure WebSphere ND environment.  Did you get this working? ... View more

I then hit the issue that the JMX agent does not work with username/password, or at least not in an WebSphere server as even with valid credentials is advised that an "unauthenticated" user was attempting to retrieving MBean information.   What did you do to get around this?  ... View more

Hi, we are also seeing the same error "unknown credentials" with out JMX connection to WebSphere.   Did you just disable security in WebSphere (BAD can not be done on our servers) or did you update some security settings in WebSphere? ... View more