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

[Jan Kalina (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-2392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13403789#comment-13403789 ] 

Jan Kalina edited comment on WFCORE-2392 at 5/9/17 1:21 PM:
------------------------------------------------------------

Reopening by Kabirs request - Kabir had to re-comment out AuthenticationTestCase:
https://github.com/jbossas/jboss-eap7/pull/1810/files
Broken by https://github.com/jbossas/jboss-eap7/pull/1811 ?


was (Author: honza889):
Reopening - Kabir had to re-comment out AuthenticationTestCase:
https://github.com/jbossas/jboss-eap7/pull/1810/files
Broken by https://github.com/jbossas/jboss-eap7/pull/1811 ?

> 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
>             Fix For: 3.0.0.Beta18
>
>
> 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)