-
Bug
-
Resolution: Done
-
Blocker
-
7.1.0.DR10, 7.1.0.DR11, 7.1.0.DR12, 7.1.0.DR13, 7.1.0.DR14
ClientLoginModule does not establish client caller identity and credentials when used to invoke EJBs backed by Elytron application-security-domain.
This issue affects easy migration to Elytron as no instructions to replace this have been provided as well as AS TS testing with Elytron profile since nearly every test case in org.jboss.as.test.integration.ejb.remote.security uses CLM to establish identity/credentials.
- blocks
-
JBEAP-9051 Tracking JIRA for tests failing with Elytron profile in AS TS
- Closed
-
JBEAP-9080 EJB security tests are failing in AS TS with Elytron profile
- Closed
- is cloned by
-
WFLY-8562 Add a test utility to ensure that tests use the ClientLoginModule approach for PicketBox deployments and the Elytron approach for Elytron deployments and update all affected tests
- Closed
- is related to
-
JBEAP-11454 In-VM calls with authenticated SecurityIdentity.runAs(Callable c) fail to authorise for asynchronous EJB calls
- Closed
- relates to
-
JBEAP-10576 Server reload missing in tearDown method of EjbElytronDomainSetup
- Closed