WFCORE-4220 SecurityCommandsTestCase fails with Elytron profile

• 
• Resolved

WFCORE-4325 Unable to run testsuite/domain tests with -Delytron

• 
• Resolved

JBEAP-8441 The RunAs annotation doesn't work in servlets with Elytron

• 
• Closed

JBEAP-9109 When Elytron is used redirect from j_security_check uses HTTP code 303

• 
• Closed

JBEAP-9146 EJB deployments with Elytron SD collides in EJB3 SD service

• 
• Closed

JBEAP-9425 Make anonymous EJB authn possible in Elytron - Get JBOSS_LOCAL_USER to behave quietly again

• 
• Closed

JBEAP-9426 Make anonymous EJB authn possible in Elytron - Ensure the default Principal name is one compatible with the servers configuration

• 
• Closed

JBEAP-9719 Clients using SecurityClientFactory are not authenticated when using Elytron

• 
• Closed

JBEAP-9752 ClientLoginModule does not work with Elytron secured EJBs for In-VM Calls e.g. Servlet to Bean or Bean to Bean

• 
• Closed

JBEAP-12056 No caller principal in new thread created from EJB (elytron)

• 
• Closed

JBEAP-9106 Servlet server distribution fails to work with Elytron - NoClassDefFoundError

• 
• Closed

JBEAP-9168 New EJB Authentication tests (in AS TS) fail with Elytron profile

• 
• Closed

JBEAP-9744 EJBContext.getCallerPrincipal behaves differently in Elytron and legacy security

• 
• Closed

JBEAP-9844 EJB call through remote-outbound-connection doesn't authenticate with Elytron

• 
• Closed

JBEAP-9070 Add assumes to failing tests in AS TS with Elytron profile

• 
• Closed

JBEAP-9071 Deployment overlay tests are failing in AS TS with Elytron profile

• 
• Closed

JBEAP-9072 Concurrent tests are failing in AS TS with Elytron profile

• 
• Closed

JBEAP-9077 IIOP Naming tests are failing in AS TS with Elytron profile

• 
• Closed

JBEAP-9080 EJB security tests are failing in AS TS with Elytron profile

• 
• Closed

JBEAP-9081 Perimeter security tests are failing in AS TS with Elytron profile

• 
• Closed

JBEAP-9111 EJB tests are failing in AS TS with Elytron profile

• 
• Closed

JBEAP-9116 SecurityAuditingTestCase fails with Elytron profile in AS TS

• 
• Closed

JBEAP-9117 Messaging SecurityTestCase fails with Elytron profile in AS TS

• 
• Closed

JBEAP-9122 RemoteAsyncInvocationTestCase fails with Elytron profile in AS TS

• 
• Closed

JBEAP-9198 RunAsPrincipalTestCase fails to deploy when Elytron profile is used

• 
• Closed

JBEAP-10566 MapBasedInitialContextEjbClientTestCase fails (with -Delytron)

• 
• Closed

WFCORE-4214 VaultPasswordsInCLITestCase fails with Elytron profile

• 
• Closed

WFCORE-4216 HTTPSManagementInterfaceTestCase fails with Elytron profile

• 
• Closed

WFCORE-4221 ReadConfigAsFeaturesStandaloneTestCase fails with Elytron profile

• 
• Closed

WFLY-11752 testsuite/integration/elytron uses directly a jboss.dist dir when set instead of its copy in the target dir

• 
• Closed

JBEAP-9113 Fix ClientCompatibilityUnitTestCase to be able to work with elytron profile in AS TS

• 
• Closed

JBEAP-9209 Verify that all tests disabled by assumeElytronProfileTestsEnabled were re-enabled

• 
• Closed

JBEAP-10655 Re-enable tests temporarily disabled in -Delytron run.

• 
• Closed

JBEAP-11560 Fix tests which currently fail with -Dwildfly.tmp.enable.elytron.profile.tests

• 
• Closed

JBEAP-9181 Ignore failing test in AS TS with Elytron profile to be able to run -Delytron on pull requests

• 
• Closed