[
https://issues.jboss.org/browse/WFCORE-2392?page=com.atlassian.jira.plugi...
]
Jan Kalina updated WFCORE-2392:
-------------------------------
Steps to Reproduce:
Checkout wildfly ladybird and run test:
{code}
cd testsuite/elytron
mvn clean test -Dtest=org.wildfly.test.integration.elytron.ejb.AuthenticationTestCase
{code}
(need to unignore tests tagged as [WFLY-7778])
was:
Checkout wildfly ladybird and run test:
{code}
cd testsuite/elytron
mvn clean test -Dtest=org.wildfly.test.integration.elytron.ejb.AuthenticationTestCase
{code}
(need to un-ignore tests tagged as [WFLY-7778])
Remoting EJB identity propagation does not work with Elytron
------------------------------------------------------------
Key: WFCORE-2392
URL:
https://issues.jboss.org/browse/WFCORE-2392
Project: WildFly Core
Issue Type: Bug
Components: Security
Reporter: Jan Kalina
Assignee: Jan Kalina
Priority: Critical
Labels: elytron-legacy-test-fails
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}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)