[jboss-jira] [JBoss JIRA] (WFLY-10410) Adding Undertow application-security-domain requires server reload although the server does not say so

Stuart Douglas (JIRA) issues at jboss.org
Sun May 20 21:56:00 EDT 2018


     [ https://issues.jboss.org/browse/WFLY-10410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stuart Douglas resolved WFLY-10410.
-----------------------------------
    Resolution: Rejected


You need to reload the properties realm after adding the user (/subsystem=elytron/properties-realm=ApplicationRealm:load()) : 

A fixed version of the test that passes without reload is at:

https://github.com/stuartwdouglas/wildfly/tree/test-fix



> Adding Undertow application-security-domain requires server reload although the server does not say so
> ------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-10410
>                 URL: https://issues.jboss.org/browse/WFLY-10410
>             Project: WildFly
>          Issue Type: Bug
>          Components: Web (Undertow)
>            Reporter: Peter Palaga
>            Assignee: Stuart Douglas
>
> I stumbled upon this when writing a security related test in WildFly Camel. When adding a new Undertow {{application-security-domain}} via a {{ServerSetupTask}}, the domain is not ready for the subsequently deployed application unless the server is reloaded. 
> I am reporting this in spite of seeing that https://issues.jboss.org/browse/WFLY-8505 and https://issues.jboss.org/browse/JBEAP-10112 were rejected as not a bug. 
> The present issue is different because the application is not deployed during the add operation and hence there is no way to reload the app.
> I believe either {{application-security-domain:add()}} should cause the server status change to {{reload-required}} or the {{application-security-domain}} should be available for the subsequent deployment without having to reload the server.
> I have written a test case - see steps to reproduce.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)


More information about the jboss-jira mailing list