Currently one has to "activate" JASPIC in WildFly by doing two things:
1. Adding a generic "dummy" security domain to standalone.xml
2. Referencing this domain from a jboss-web.xml within the application archive
I wonder if it would make sense to put the generic jaspic security domain by default in standalone.xml. It's always the same anyway. With the domain present in a stock WildFly it's much easier for people to start with JASPIC on WildFly.
It concerns this fragment:
<security-domain name="jaspitest" cache-type="default">
<login-module code="Dummy" flag="optional"/>