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

Unclear failure description when removing elytron policy referenced as the default-policy

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.1.0.ER3
    • 7.1.0.ER1
    • Security
    • None

      when user wants to remove a jacc-policy referenced as default-policy, for example

      /profile=full/subsystem=elytron/policy=policy1:read-resource
      {
          "outcome" => "success",
          "result" => {
              "custom-policy" => undefined,
              "default-policy" => "policy-teste",
              "jacc-policy" => [
                  {
                      "name" => "policy-teste",
                      "module" => "modulo-policy",
                      "configuration-factory" => "OutroFactory1",
                      "policy" => "PolicyM2"
                  },
                  {
                      "name" => "policy123",
                      "module" => "modulo-123",
                      "configuration-factory" => "OutroFactory1",
                      "policy" => "PolicyM2"
                  },
                  {
                      "name" => "outro_policy123",
                      "module" => "modulo-123",
                      "configuration-factory" => "OutroFactory1",
                      "policy" => "PolicyM2"
                  }
              ]
          }
      }
      
      /profile=full/subsystem=elytron/policy=policy1:list-remove(name=jacc-policy,index=0)
      {
          "outcome" => "failed",
          "failure-description" => {"domain-failure-description" => "Could find policy provider with name [policy-teste]"},
          "rolled-back" => true
      }
      

      The message should say the jacc-policy is used as default-policy.

              mstefank Martin Stefanko
              mstefank Martin Stefanko
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: