Disabling Security on http-invoker EJB for JBoss EAP 7.2

Solution Verified - Updated -

Issue

  • Disabling security doesn't allow the EJB client to connect
  • After disabling security with

    • /subsystem=remoting/http-connector=http-remoting-connector:undefine-attribute(name=security-realm)

    Or

    • /subsystem=undertow/server=default-server/host=default-host/setting=http-invoker:write-attribute(name=security-realm)

    I get this exception in server.log:

    ERROR [org.jboss.as.ejb3.invocation] (default task-1) {} WFLYEJB0034: EJB Invocation failed on component ServiceBean for method public abstract some.class.package.Message some.class.package.RemoteService.getMessage(some.class.package.Message): java.lang.IllegalArgumentException: Parameter 'identity' may not be null
        at org.wildfly.common.Assert.checkNotNullParamChecked(Assert.java:71)
        at org.wildfly.common.Assert.checkNotNullParam(Assert.java:49)
        at org.wildfly.security.auth.server.SecurityDomain.forIdentity(SecurityDomain.java:187)
        at org.jboss.as.security.service.SimpleSecurityManager.push(SimpleSecurityManager.java:313)
    

Environment

  • Red Hat JBoss Enterprise Application Platform
    • 7.2
  • EJBs via http-invoker

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content