-
Task
-
Resolution: Done
-
Major
-
None
-
False
-
False
-
-
-
-
-
-
+
-
When we run the testsuite using the 'elytron' profile (i.e. by passing -Delytron) a number of testsuite modules alter the config of the server being tested by invoking CLI scripts prior to starting the tests. These scripts produce good results on SE 11 or earlier, but for SE 17 we need further modifications, as legacy security resource like kernel security realms are not supported.
Task here is to develop alternative scripts that will work on SE 17 and to ensure those are applied when SE 17 is being used to run the tests.
The intent is not to change the existing scripts, as those more closely match what the docs/examples/enable-elytron.cli script does, so we should continue to test kind of setup when SE 17 isn't used.
- blocks
-
JBEAP-22844 (7.4.z) Update testsuite/integration/multinode tests to run on SE 17
- Closed
-
JBEAP-22845 (7.4.z) Update testsuite/integration/manualmode tests to run on SE 17
- Closed
- is related to
-
JBEAP-23481 [QE](7.4.z) web-enable-elytron.cli.se17 script doesn't remove all legacy security configuration
- Closed
-
JBEAP-22684 (7.4.z) WFLY-15264 - Update EE security tests for removal of legacy security
- Closed
-
JBEAP-22865 (7.4.z) WFLY-15179 - Update SSLEJBRemoteClientTestCase to use Elytron SSLContext when running on SE17
- Closed
-
JBEAP-22866 (7.4.z) Fix GetCallerPrincipalWithNoDefaultSecurityDomainTestCase on SE17.
- Closed
-
JBEAP-22867 (7.4.z) WFLY-15171 - On SE 17 update EJBClientDescriptorTestCase to use an authentication context for the outbound connections.
- Closed
-
JBEAP-22868 (7.4.z) WFLY-15172 - Update ListenerTestCase to use Elytron defined SSLContext on SE 17
- Closed
-
JBEAP-22869 (7.4.z) Fix org.jboss.as.test.integration.ws.wsse.trust failures on SE 17
- Closed
- relates to
-
JBEAP-22683 (7.4.z) WFLY-15263 - Update audit logging tests for lack of legacy security
- Closed