<div dir="ltr"><div>I think you should be able to modify it programmatically using a ServletExtension and changing <br><br>io.undertow.servlet.api.DeploymentInfo.authorizationManager from the default.<br><br></div>Stuart<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Aug 19, 2016 at 6:50 PM, arjan tijms <span dir="ltr"><<a href="mailto:arjan.tijms@gmail.com" target="_blank">arjan.tijms@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div>In org.wildfly.extension.<wbr>undertow.deployment.<wbr>UndertowDeploymentInfoService.<wbr>handleJACCAuthorization I found the following comment:</div><div><br></div><div> // TODO make the authorization manager implementation configurable in Undertow or jboss-web.xml<br></div><div><br></div><div>Wonder if that TODO is still on the radar. </div><div><br></div><div>Would be quite an improvement if an application could declare itself that it wanted to use the Java EE authorization module (JACC), which would hold for either the default JACC module that JBoss/WildFly ships (and initializes) or a user provide one.</div><div><br></div><div>Thoughts?</div><div><br></div><div>Kind regards,</div><div>Arjan Tijms</div><div><br></div><div><br></div></div>
<br>______________________________<wbr>_________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org">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/<wbr>mailman/listinfo/wildfly-dev</a><br></blockquote></div><br></div>