-
Bug
-
Resolution: Done
-
Major
-
None
-
None
Changing attribute changing http-server-mechanism-factory of http-authentication-factory ends in reload-required state even though header allow-resource-service-restart=true is used
[standalone@localhost:9990 /] /subsystem=elytron/http-authentication-factory=application-http-authentication:write-attribute(name=http-server-mechanism-factory, value=global){allow-resource-service-restart=true}
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
Header should work as attribute is declared as "restart-required" => "resource-services"
"http-server-mechanism-factory" => { "type" => STRING, "description" => "The HttpServerAuthenticationMechanismFactory to associate with this resource", "expressions-allowed" => false, "required" => true, "nillable" => false, "capability-reference" => "org.wildfly.security.http-server-mechanism-factory", "min-length" => 1L, "max-length" => 2147483647L, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "resource-services" }
And according to documentation [1]:
resource-services – The operation can only immediately update the persistent configuration; applying the operation to the runtime will require a subsequent restart of some services associated with the resource. If the operation includes the request header "allow-resource-service-restart" => true, the handler for the operation will go ahead and restart the runtime service. Otherwise executing the operation will put the server into a "reload-required" state. (See the discussion of "all-services" above for more on the "reload-required" state.)
[1] https://docs.jboss.org/author/display/WFLY10/Description+of+the+Management+Model
- clones
-
-
- Closed
-