[
https://issues.jboss.org/browse/WFCORE-3041?page=com.atlassian.jira.plugi...
]
Pedro Igor commented on WFCORE-3041:
------------------------------------
[~brian.stansberry] and [~michpetrov],I was on PTO, sorry for the late reply. It seems you
already did the black magic for WFCORE-3041. Is there anything else missing ?
Regarding your question about multiple policies, the requirement came from
https://issues.jboss.org/browse/EAP7-651. After reading your comments and changes, I think
we are still good and aligned with the functional objective of original issue.
Thanks for looking this and sorry for any confusion.
Cannot add policy resource with no parameter
--------------------------------------------
Key: WFCORE-3041
URL:
https://issues.jboss.org/browse/WFCORE-3041
Project: WildFly Core
Issue Type: Bug
Components: Security
Reporter: Claudio Miranda
Assignee: Brian Stansberry
Priority: Blocker
Fix For: 3.0.6.Final, 4.0.0.Alpha1
subsystem=elytron/policy resources has no required attributes, but it fails to add a
resource with no parameters.
{code}
/profile=full/subsystem=elytron/policy=policy_test:add
{
"outcome" => "failed",
"result" => undefined,
"failure-description" => {"WFLYDC0074: Operation failed or was
rolled back on all servers. Server failures:" => {"server-group" =>
{"main-server-group" => {"host" => {"master" =>
{"server-one" => "Could find policy provider with name
[policy_test]"}}}}}},
"rolled-back" => true,
"server-groups" => {"main-server-group" =>
{"host" => {"master" => {"server-one" =>
{"response" => {
"outcome" => "failed",
"failure-description" => "Could find policy provider with name
[policy_test]",
"rolled-back" => true
}}}}}}
}
{code}
To add is necessary to inform either custom-policy or jacc-policy
{code}
/profile=full/subsystem=elytron/policy=policy2:add(jacc-policy=[{name=policy2}])
{
"outcome" => "success",
"result" => undefined,
"server-groups" => {"main-server-group" =>
{"host" => {"master" => {"server-one" =>
{"response" => {
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}}}}}}
}
{code}
There is also a problem related to "default-policy" being set to a non existent
policy.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)