-
Bug
-
Resolution: Done
-
Major
-
7.1.0.ER1
-
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.
- clones
-
WFCORE-3093 Unclear failure description when removing elytron policy referenced as the default-policy
- Resolved
- is incorporated by
-
JBEAP-11931 (7.1.0) Upgrade to WildFly Core to 3.0.0.Beta30
- Closed