[wildfly-dev] Authorization manager configurable in jboss-web.xml?

[arjan tijms]

Hi,

I guess that should work and for some situations it's even the better
solution. Still, a jboss-web.xml option would be quite a bit easier.

Kind regards,
Arjan Tijms


On Sat, Aug 20, 2016 at 12:35 AM, Stuart Douglas <stuart.w.douglas at gmail.com
> wrote:

> I think you should be able to modify it programmatically using a
> ServletExtension and changing
>
> io.undertow.servlet.api.DeploymentInfo.authorizationManager from the
> default.
>
> Stuart
>
> On Fri, Aug 19, 2016 at 6:50 PM, arjan tijms <arjan.tijms at gmail.com>
> wrote:
>
>> Hi,
>>
>> In org.wildfly.extension.undertow.deployment.UndertowDeploym
>> entInfoService.handleJACCAuthorization I found the following comment:
>>
>>   // TODO make the authorization manager implementation configurable in
>> Undertow or jboss-web.xml
>>
>> Wonder if that TODO is still on the radar.
>>
>> 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.
>>
>> Thoughts?
>>
>> Kind regards,
>> Arjan Tijms
>>
>>
>>
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20160820/88be7bfe/attachment.html