<div dir="ltr">Hi,<div><br></div><div>The jaspitest domain is to allow a (servlet) application to "activate" JASPIC and install JASPIC authentication modules without having to modify the server distribution.</div><div><br></div><div>For almost as long as JBoss supports JASPIC the promise has been that such explicit activation would some time in the future not be needed anymore. Initially the promise was that with Undertow this would be fixed, but when it wasn't Elytron would address it. Now that Elytron is there I'm not sure if it's indeed finally not needed anymore. Darran Lofthouse should be the one who knows.</div><div><br></div><div>If Elytron still requires the manual "activation" of JASPIC, then the jaspitest domain is likely needed. Both Tomcat and Jetty also support (the Servlet Container Profile of) JASPIC.</div><div><br></div><div>Kind regards,</div><div>Arjan</div><div><br></div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr">On Tue, Jun 19, 2018 at 3:54 PM Yeray Borges <<a href="mailto:yborgess@redhat.com">yborgess@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Hello everyone, <br>
<br>
I'm doing a comparison between the different server configuration
files generated in normal distribution and servlet-distribution,
basically working on [1].<br>
<br>
The security subsystem in the servlet distribution does not have
these security domains configured whereas they are in the normal
distribution:
<br>
<br>
<font face="Courier New, Courier, monospace"><subsystem
xmlns="urn:jboss:domain:security:2.0"><br>
<security-domains><br>
...<br>
<security-domain name="jboss-web-policy"
cache-type="default"><br>
<authorization><br>
<policy-module code="Delegating"
flag="required"/><br>
</authorization><br>
</security-domain><br>
<security-domain name="jboss-ejb-policy"
cache-type="default"><br>
<authorization><br>
<policy-module code="Delegating"
flag="required"/><br>
</authorization><br>
</security-domain><br>
<security-domain name="jaspitest" cache-type="default"><br>
<authentication-jaspi><br>
<login-module-stack name="dummy"><br>
<login-module code="Dummy" flag="optional"/><br>
</login-module-stack><br>
<auth-module code="Dummy"/><br>
</authentication-jaspi><br>
</security-domain><br>
<security-domains> </font><br>
<br>
I understand jboss-ejb-policy should not be configured because the
servlet-distribution does not use ejbs, but what about jaspitest?
<br>
I have no clue if it has to be included or not in the
servlet-distribution. <br>
<br>
Do you know if we should include it?
<br>
<br>
Regards,<br>
Yeray<br>
<br>
[1] <a class="m_-8683432040772287223moz-txt-link-freetext" href="https://issues.jboss.org/browse/WFLY-10421" target="_blank">https://issues.jboss.org/browse/WFLY-10421</a><br>
</div>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a></blockquote></div>