-
Bug
-
Resolution: Won't Do
-
Critical
-
None
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:
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)
- blocks
-
WFLY-8720 Fix and unignore tests for switching identities in Elytron
-
- Closed
-
- is cloned by
-
JBEAP-8066 Remoting EJB identity propagation does not work with Elytron
-
- Closed
-
- is related to
-
WFLY-7041 Add testing for Web -> EJB Identity Propagation
-
- Closed
-
- relates to
-
WFCORE-2407 ReAuth does not work with Elytron
-
- Resolved
-