[ https://issues.jboss.org/browse/WFLY-7778?page=com.atlassian.jira.plugin.... ] Jan Kalina updated WFLY-7778: ----------------------------- Description: Even througth succesful obtaining LoginContext, identity is not propagated in EJB call. Identity is unauthorized on server side. *Remoting does not work because it is not implemented yet* - this issue created primary for tests ignore issue reference. Often error message: {code:java} SaslException: Authentication failed: all available authentication mechanisms failed: JBOSS-LOCAL-USER: Server rejected authentication DIGEST-MD5: Server rejected authentication] at org.wildfly.naming.client.remote.RemoteNamingProvider.getPeerIdentityForNaming(RemoteNamingProvider.java:110) {code} was: Even througth succesful obtaining LoginContext, identity is not propagated in EJB call. Identity is unauthorized on server side. *Remoting does not work because it is not implemented yet* - this issue created primary for tests ignore issue reference. Often error message: {code:java} SaslException: Authentication failed: all available authentication mechanisms failed: JBOSS-LOCAL-USER: Server rejected authentication DIGEST-MD5: Server rejected authentication] {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)