Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-10410

Adding Undertow application-security-domain requires server reload although the server does not say so

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Major
    • None
    • None
    • Web (Undertow)
    • None
    • Hide 
      cd wildfly
git remote add ppalaga https://github.com/ppalaga/wildfly.git
git fetch ppalaga
git checkout -b 180520-application-security-domain ppalaga/180520-application-security-domain

mvn clean install -Dtest=WebSecurityBASICCustomDomainTestCase -DfailIfNoTests=false -DallTests

      ACTUAL: WebSecurityBASICCustomDomainTestCase.basic() test fails getting 401 instead of 200. In the output of the test in testsuite/integration/web/target/surefire-reports/null-output.txt the status of the server after the add operation is running.

      EXPECTED: Either (a) WebSecurityBASICCustomDomainTestCase.basic() passes as is and the status of the server after the add operation is running
      or (b) WebSecurityBASICCustomDomainTestCase.basic() fails as it does but the status of the server after the add operation is reload-required.

      Note that when executeReloadAndWaitForCompletion() is uncommented in https://github.com/ppalaga/wildfly/commit/570a0713b57abeb9cded976a75180784ea26a6a2#diff-83a2b164997ea365b5f5b36adb2fd205R143 the basic test passes.

      Show
      cd wildfly git remote add ppalaga https: //github.com/ppalaga/wildfly.git git fetch ppalaga git checkout -b 180520-application-security-domain ppalaga/180520-application-security-domain mvn clean install -Dtest=WebSecurityBASICCustomDomainTestCase -DfailIfNoTests= false -DallTests ACTUAL: WebSecurityBASICCustomDomainTestCase.basic() test fails getting 401 instead of 200 . In the output of the test in testsuite/integration/web/target/surefire-reports/null-output.txt the status of the server after the add operation is running . EXPECTED: Either (a) WebSecurityBASICCustomDomainTestCase.basic() passes as is and the status of the server after the add operation is running or (b) WebSecurityBASICCustomDomainTestCase.basic() fails as it does but the status of the server after the add operation is reload-required . Note that when executeReloadAndWaitForCompletion() is uncommented in https://github.com/ppalaga/wildfly/commit/570a0713b57abeb9cded976a75180784ea26a6a2#diff-83a2b164997ea365b5f5b36adb2fd205R143 the basic test passes.

    Description

      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.

      Attachments

        Activity

          People

            sdouglas1@redhat.com Stuart Douglas
            ppalaga Peter Palaga
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: