Hello All,
This is somewhat of a follow up to the "Disabling of Security Manager in latest SE 24". I wanted to start a new thread because what this touches on is a bit different.

Just an FYI for those projects using GitHub Actions. If you use Temurin, you can use 24-ea as the version to test against. 

One thing to note is WildFly will not currently boot with the latest version of Java 24 due to MODULES-453 [1].

Also, the standard WildFly configuration will not boot, see WFCORE-7059 [2], but you can simply workaround that by removing the jacc default policy, in most cases. The simple CLI command is:
/subsystem=elytron/policy=jacc:remove

I've not done full testing with this solution, but it seems to work for the tests I've done.

If you're using WildFly Arquillian there is one additional issue [3]. I plan to do another release of the wildfly-launcher API, new home, new GAV, and a new WildFly Arquillian release by the end of this week.

[1]: https://issues.redhat.com/browse/MODULES-453
[2]: https://issues.redhat.com/browse/WFCORE-7059 
[3]: https://github.com/wildfly/wildfly-launcher/issues/6


James R. Perkins

Principal Software Engineer

Red Hat