Authentication (or SASL configuration?) seems to be leaking between EJB remote calls.
It causes authentication failures in subsequent calls.
I have following scenario:
EJB Client --> EntryBean on server1 --> WhoAmIBean on server2
Both the EJB Client and the EntryBean use Elytron API (AuthenticationContext+AuthenticationConfiguration) to provide valid authentication configuration.
The full scenario (including bean lookups) is repeated several times with different Elytron AuthenticationConfigurations used (always a valid one).
When scenarios run isolated (reload server between runs) they pass. Nevertheless when they run in sequence without reloads, then some combination fails.
- is caused by
-
REM3-296 Ensure that a SASL mechanism that failed when establishing the initial connection doesn't get excluded in subsequent shared-connection authentication attempts
- Resolved
- is incorporated by
-
JBEAP-12582 Upgrade to jboss-remoting 5.0.0.Final
- Closed