Wildfly 26.1.2 Cannot anymore configure EJB remote connections from a remote server

[ralfbat...@gmail.com]

I tried to upgrade from Wildfly 24 to Wildfly 26, and apparently, I can't define anymore the security-realm under the management section. 

Looking at the documentation in chapter 19.9  'Create a security realm on the client server', it still specifies this place: https://docs.wildfly.org/26.1/Developer_Guide.html#EJB_invocations_from_a_remote_server_instance

 I get this error message:

OPVDX001: Validation error in standalone-full-backend-26-DEV.xml ---------------
|
|  85:     </role-mapping>
|  86: </access-control>
|  87: <security-realms>
|                       ^^^^ 'security-realms' isn't an allowed element here
|                            
|                            Elements allowed here are: access-control, audit-log,
|                              configuration-changes, identity, management-interfaces
|
|  88:     <security-realm name="ejb-security-realm">
|  89:         <server-identities>
|  90:             <secret value="xxxxxxxxxxxxxx"/>
|
| The primary underlying error message was:
| > ParseError at [row,col]:[87,26]
| > Message: WFLYCTL0198: Unexpected element
| >   '{urn:jboss:domain:19.0}security-realms' encountered
|
|-------------------------------------------------------------------------------

I guess it has to be configured differently but I can't find how.

Thanks for any help.

Ralf

[Wolfgang]

Hi Ralf,

it seems you still use the old style security configuration, which was removed in recent WildFly servers. You now have to use Elytron.

Take a look at the doc: https://docs.wildfly.org/26.1/WildFly_Elytron_Security.html

This quickstarts might help: https://github.com/wildfly/quickstart/tree/26.x/ejb-security-programmatic-auth

If you search in "standalone.xml" of WildFly 24 und WildFly 26 for "Management Realm", you will see where it is declared now.

Hope this helps

Wolfgang