login is ok now using the following configuration
server config:
client initial context:
ctx.put("java.naming.factory.initial", "org.jboss.naming.remote.client.InitialContextFactory");
ctx.put("jboss.naming.client.ejb.context", true); // can not be in jndi.properties. Requieres boolean, does not accept String
ctx.put(InitialContext.PROVIDER_URL, "remote://localhost:4447");
ctx.put(InitialContext.SECURITY_PRINCIPAL, "test");
ctx.put(InitialContext.SECURITY_CREDENTIALS, "tset");
jboss-ejb-client:
remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED=false
remote.connections=default
remote.connection.default.host=localhost
remote.connection.default.port=4447
remote.connection.default.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS=true
remote.connection.default.connect.options.org.xnio.Options.SASL_DISALLOWED_MECHANISMS=JBOSS-LOCAL-USER
remote.connection.default.connect.options.org.xnio.Options.SASL_POLICY_NOPLAINTEXT=false
remote.connection.default.username=test
remote.connection.default.password=tset
The key thing was that the username/password must be passed in on 2 places: in the jboss-ejb-client file AND in InitialContext. Is this how it should be or does anyone knows a better solution?
Redirecting the ApplicationRealm to my-security-domain still doesn't work. How has this to be done?
<security-realm name="ApplicationRealmEdis">
<authentication>
<jaas name="edis-security-domain"/>
</authentication>
</security-realm>