[jboss-jira] [JBoss JIRA] (WFCORE-2500) Elytron, changing http-server-mechanism-factory of http-authentication-factory ends in reload-required state
Brian Stansberry (JIRA)
issues at jboss.org
Fri May 5 22:54:03 EDT 2017
[ https://issues.jboss.org/browse/WFCORE-2500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Stansberry updated WFCORE-2500:
-------------------------------------
Fix Version/s: 3.0.0.Beta19
(was: 3.0.0.Beta18)
> Elytron, changing http-server-mechanism-factory of http-authentication-factory ends in reload-required state
> ------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-2500
> URL: https://issues.jboss.org/browse/WFCORE-2500
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Martin Choma
> Assignee: Tomas Hofman
> Fix For: 3.0.0.Beta11, 3.0.0.Beta19
>
>
> 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
> {code}
> [standalone at 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"
> }
> }
> {code}
> Header should work as attribute is declared as {{"restart-required" => "resource-services"}}
> {code}
> "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"
> }
> {code}
> 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
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
More information about the jboss-jira
mailing list