This does not include RBAC which is justified as having it's own set of tests.

Across WildFly our testsuites are taking an increasing amount of time to execute, one of the reasons for this is as we need to test a new feature or bug fix we add a new test case, this often involves reconfiguring and starting a server for testing followed by a clean up.

For TLS and authentication we should instead have a single suite, we don't need to worry about differences between Elytron and legacy as legacy is now being removed.

Some of the permutations we have:

• One way TLS, Two Way TLS, No TLS
• Direct https and redirects from http to https
• Native interface and http interface
• Default Authentication
• Disable local auth
• Force username password auth
• Client Cert
• ModelControllerClient vs CLI

Future test development should aim to extend this suite rather than add an entirely new test for a small scenario.