[jboss-jira] [JBoss JIRA] (WFCORE-2392) Remoting EJB identity propagation does not work with Elytron

Jan Kalina (JIRA) issues at jboss.org
Wed Mar 15 13:09:00 EDT 2017


     [ https://issues.jboss.org/browse/WFCORE-2392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

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 un-ignore tests tagged as [WFLY-7778])

  was:
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.AuthenticationTestCase.testAuthentication()
org.jboss.as.test.integration.ejb.security.AuthenticationTestCase.testAuthentication_BadPwd()
org.jboss.as.test.integration.ejb.security.AuthenticationTestCase.testAuthentication_TwoBeans()
org.jboss.as.test.integration.ejb.security.AuthenticationTestCase.testAuthentication_TwoBeans_ReAuth_BadPwd()
(and a lot of other, most of tests using EJB)

UPDATE:
https://github.com/wildfly-security-incubator/wildfly/pull/102 instead and following with -Delytron option:
org.jboss.as.test.integration.ejb.security.AuthenticationElytronTestCase.testAuthentication()



> 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)


More information about the jboss-jira mailing list