Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-3112

Removing of non-existing security-domain subresource should fail with an error

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Minor
    • 7.1.0.DR1
    • 7.0.0.ER4
    • Security
    • None
    • DR1
    • Hide

      Start server and run following CLI command:

      ./jboss-cli.sh -c '/subsystem=security/security-domain=jboss-web-policy/authorization=classic/policy-module=nonExistent:remove()'
      Show
      Start server and run following CLI command: ./jboss-cli.sh -c '/subsystem=security/security-domain=jboss-web-policy/authorization=classic/policy-module=nonExistent:remove()'

    Description

      In case when non-existent policy-module is removed through Management CLI, operation should finish with failure. However it finishes with outcome success and nothing is changed. It can be confusing since wrong command seems same as correct command.

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-1523 RestartParentResourceRemoveHandler should fail when removing non-existing resources

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved
          is duplicated by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-3082 Removing of non-existent login-module finishes with outcome success

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-5293 Upgrade WildFly Core from 2.1.6.Final-redhat-1 to 2.2.0.CR7

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-3113 Removing of non-existent mapping-module finishes with outcome success

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Verified

          Activity

            People

              spyrkob Bartosz Spyrko-Smietanko
              olukas Ondrej Lukas (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: