-
1. Re: Remote EJB connection to Wildfly
milan.tomic Aug 30, 2017 7:24 AM (in response to milan.tomic)It seems that the above exception came because I was using JNDI string starting with "ejb:..." to call my remote EJB. Now I am using "java:global..." and I get this exception:
javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed:
JBOSS-LOCAL-USER: javax.security.sasl.SaslException: Failed to read server challenge [Caused by java.io.FileNotFoundException:
How can I disable security when invoking remote EJBs? I have found how to remove "security-realm" attribute (ApplicationRealm) from http-remoting-connector:
JBoss AS 7.1 - Disable Remote EJB Security Realm
but it seems not to work with Wildfly 10.1 because I get an exception:
javax.naming.NameNotFoundException: global/...MyEJBRemoteInterface...
at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184)
at org.jboss.naming.remote.protocol.v1.Protocol$1.handleServerMessage(Protocol.java:127)
at org.jboss.naming.remote.protocol.v1.RemoteNamingServerV1$MessageReciever$1.run(RemoteNamingServerV1.java:73)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Of course, when Wildfly starts I can see JNDI of my EJB listed there which should indicate that EJB is deployed but why do I then get NameNotFoundException if I remove "security-realm" attribute?
I do not have any errors or warnings in my Wildfly logs during startup.