I will have a look at what we can do, as we are transitioning to Elytron long term we should be aiming to avoid all workarounds like this.


On 04/11/15 09:37, arjan tijms wrote:

Hi,

On Fri, Oct 30, 2015 at 10:19 AM, arjan tijms <arjan.tijms@gmail.com
<mailto:arjan.tijms@gmail.com>> wrote:

    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.


Anyone has any thoughts on this?

WildFly currently has one of the best JASPIC implementations out there,
but this relatively tiny problem is a big hurdle for usability, and
especially impedes using WildFly for JSR 375 demonstrations.

Hope something can be done here.

Kind regards,
Arjan Tijms




    It concerns this fragment:

      <security-domain name="jaspitest" cache-type="default">
         <authentication-jaspi>
             <login-module-stack name="dummy">
                 <login-module code="Dummy" flag="optional"/>
             </login-module-stack>
             <auth-module code="Dummy"/>
         </authentication-jaspi>
      </security-domain>

    Kind regards,
    Arjan Tijms