[
https://issues.jboss.org/browse/WFLY-7778?page=com.atlassian.jira.plugin....
]
Jan Kalina updated WFLY-7778:
-----------------------------
Steps to Reproduce:
Tests: (after modification to use Elytron instead of legacy subystem:
https://github.com/wildfly-security-incubator/wildfly/pull/56 )
org.jboss.as.test.integration.ejb.security.testAuthentication()
org.jboss.as.test.integration.ejb.security.testAuthentication_BadPwd()
org.jboss.as.test.integration.ejb.security.testAuthentication_TwoBeans()
org.jboss.as.test.integration.ejb.security.testAuthentication_TwoBeans_ReAuth_BadPwd()
(and a lot of other, most of tests using EJB)
was:
Tests: (after modification to use Elytron instead of legacy subystem)
org.jboss.as.test.integration.ejb.security.testAuthentication()
org.jboss.as.test.integration.ejb.security.testAuthentication_BadPwd()
org.jboss.as.test.integration.ejb.security.testAuthentication_TwoBeans()
org.jboss.as.test.integration.ejb.security.testAuthentication_TwoBeans_ReAuth_BadPwd()
(and a lot of other, most of tests using EJB)
Remoting identity propagation does not work with Elytron
--------------------------------------------------------
Key: WFLY-7778
URL:
https://issues.jboss.org/browse/WFLY-7778
Project: WildFly
Issue Type: Bug
Components: Security
Reporter: Jan Kalina
Assignee: Jan Kalina
Priority: Critical
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)