-
Bug
-
Resolution: Done
-
Major
-
7.1.5.GA, 7.2.0.GA
-
None
Spring Security uses HttpServletRequest.login() to set the Principal.
In general, programmatic web authentication via HttpServletRequest.login() works fine, but when Elytron Identity Propagation is configured, the Identity that gets set by HttpServletRequest.login() does not get propagated.
It results in:
org.jboss.ejb.client.RequestSendFailedException: EJBCLIENT000409: No more destinations are available at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:592) at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:528) at org.jboss.ejb.protocol.remote.RemotingEJBClientInterceptor.handleInvocationResult(RemotingEJBClientInterceptor.java:56) ... Suppressed: org.jboss.ejb.client.RequestSendFailedException at org.jboss.ejb.protocol.remote.RemoteEJBReceiver$1.handleFailed(RemoteEJBReceiver.java:101) ... Caused by: javax.security.sasl.SaslException: Authentication failed: none of the mechanisms presented by the server (PLAIN) are supported at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:444) ...
- incorporates
-
ELY-1464 Programatic authentication should be caching the SecurityIdentity not the name of the identity
- Resolved
-
ELY-1747 Programmatic web authentication does not save the password as a credential
- Resolved
- is incorporated by
-
JBEAP-16146 (7.2.z) Upgrade Elytron from 1.6.1.Final to 1.6.2.Final
- Closed
- is related to
-
WFLY-11787 Add test case for JBEAP-16152: identity propagation does not work when programmatic web authentication via HttpServletRequest.login() is used
- Reopened
- relates to
-
WFLY-11787 Add test case for JBEAP-16152: identity propagation does not work when programmatic web authentication via HttpServletRequest.login() is used
- Reopened
- links to