What causes "java.lang.SecurityException: Failed to authenticate principal=null, securityDomain=jmx-console" in JBoss EAP 4 or 5?

Solution Verified - Updated -

Issue

When invoking operations dependent on JMX MBeans (for example, dm.getAvailableModules(ModuleType.EAR, targets)), exceptions similar to the following are thrown:

15:56:56,703 ERROR [JMXTarget] Cannot get available modules
java.lang.SecurityException: Failed to authenticate principal=null, securityDomain=jmx-console

Or:

java.lang.SecurityException: Failed to authenticate principal=null, securityDomain=jmx-console
      at org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke
      at org.jboss.mx.server.Invocation.invoke
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke
      at org.jboss.mx.server.MBeanServerImpl.invoke
      at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke
      ...
      javax.servlet.http.HttpServlet.service
      ...

Environment

  • JBoss Enterprise Application Platform (EAP) 4.3
  • JBoss Enterprise Application Platform (EAP) 5.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.