The notion of the application security domain resources was something we introduced so we could support legacy security by default and provide the administrator a mechanism to switch to using WildFly Elytron - now that WildFly 11 is out I am looking at how we can add configuration directly to the deployment.

Additionally for my work after WildFly 11 I am also going to be looking at the options to inject a few key WildFly Elytron resources.

Overall rather than adding further service dependencies, could it be better to attach something to the DeploymentUnit so it can be used later?

Regards,

Darran Lofthouse.

On Wed, 8 Nov 2017 at 01:47 Jim Ma <ema@redhat.com> wrote:

WebSerivce subsystem has a user reported issue [1] which ws endpoint can't declare an undertow subsystem application security domain in jboss-web.xml. I had a quick look and it looks we need an injector to get undertow's ApplicationSecurityDomain and finally get the elytron security domain like what we handle ejb application security domain right now [2].
To make this work, I write some workaround code [3], and this may better explain what ws integration code expects to fix this issue. Darren and Stuart, can you please have a look and let me know your ideas and thoughts about this issue?

[1]https://developer.jboss.org/message/977628
[2] https://github.com/wildfly/wildfly/blob/master/webservices/server-integration/src/main/java/org/jboss/as/webservices/service/EndpointService.java#L100
[3] https://github.com/jimma/wildfly/commit/d93b8ac89e388c54a10ce627780486143267e052

Thanks,
Jim

_______________________________________________
wildfly-dev mailing list
wildfly-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev