[wildfly-dev] Adding additional security domain to standalone.xml?

arjan tijms arjan.tijms at gmail.com
Wed Nov 4 04:37:49 EST 2015


On Fri, Oct 30, 2015 at 10:19 AM, arjan tijms <arjan.tijms at 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20151104/71b5a674/attachment-0001.html 

More information about the wildfly-dev mailing list