title: Why is "jaspitest" needed in a Java EE web application?
body: <p>I am slowly getting into the dark world of Java EE and understanding Application Servers, Containers and Web applications.</p>
  <p>Looking through existing codebases I can see production code referencing &quot;jaspitest&quot; in <code>jboss-web.xml</code></p>
  <p>A search on Github, it appears many other projects, reference this as well:</p>
  <p><a href="https://github.com/search?q=%22jaspitest%22&amp;type=code" rel="nofollow noreferrer">https://github.com/search?q=&quot;jaspitest&quot;&amp;type=code</a></p>
  <p>In the Wildfly configuration it is defined as this:</p>
  <pre><code>&lt;security-domain name=&quot;jaspitest&quot; cache-type=&quot;default&quot;&gt;
                      &lt;authentication-jaspi&gt;
                          &lt;login-module-stack name=&quot;dummy&quot;&gt;
                              &lt;login-module code=&quot;Dummy&quot; flag=&quot;optional&quot;/&gt;
                          &lt;/login-module-stack&gt;
                          &lt;auth-module code=&quot;Dummy&quot;/&gt;
                      &lt;/authentication-jaspi&gt;
                  &lt;/security-domain&gt;
  </code></pre>
  <p>A simple experiment, deleting this reference to jaspitest breaks all authentication.</p>
  <p>What is the purpose of this default configuration, and why is it so prevalent?</p>
  <p>What is the historical context of this?</p>
  <p>Thanks</p>