-
Bug
-
Resolution: Done
-
Blocker
-
None
Sticky authentication and connection sharing is not working correctly. When an object such as an EJB proxy, naming context, or transaction controller (like UserTransaction) is looked up via JNDI where the context has authentication configuration associated with it, that configuration should be sticky to the EJB proxy, context, or transaction controller. When such entities are looked up without security information, then authentication information should be looked up from the calling context's security configuration.
- blocks
-
JBEAP-8635 Recovery doesn't work when transaction is propagated thru EJB remoting
- Closed
-
JBEAP-9654 Scoped EJB client context from EAP 7.1 can't invoke stateful beans on EAP 7.0
- Closed
-
JBEAP-9662 Invocations on UserTransaction obtained from InitialContext don't take user credentials into account
- Closed
-
JBEAP-9692 Remote-outbound-connection with legacy-style configuration only allows JBOSS-LOCAL-USER auth mechanism
- Closed
-
JBEAP-9713 Remote outbound connection with authentication-context cannot be used for remote EJB calls
- Closed
-
JBEAP-10090 Attribute allow-sasl-mechanisms is ignored in Elytron Authentication Configuration
- Closed
- causes
-
JBEAP-10284 Transaction invoked by client does not finish commitment in ejb-multi-server quickstart when using scoped context
- Closed
- is caused by
-
EJBCLIENT-210 Sticky authentication should be keyed by URI + auth conf
- Resolved
-
REM3-266 Connection sharing APIs are incorrect
- Resolved
-
WFNC-27 Naming providers need to have a sticky authentication association
- Resolved
-
WFTC-18 Use sticky auth from naming context when available
- Resolved