-
Bug
-
Resolution: Done
-
Major
-
None
-
None
If I try to change Elytron default-authentication-context server ends in reload-required state.
/subsystem=elytron/authentication-context=auth-context:add() /subsystem=elytron:write-attribute(name=default-authentication-context,value=auth-context) { "outcome" => "success", "response-headers" => { "operation-requires-reload" => true, "process-state" => "reload-required" } }
However attribute default-authentication-context is marked as "restart-required" => "no-services" in model
/subsystem=elytron:read-resource-description(recursive=false) { ... "default-authentication-context" => { "type" => STRING, "description" => "The default authentication context to be associated with all deployments.", "expressions-allowed" => false, "required" => false, "nillable" => true, "capability-reference" => "org.wildfly.security.authentication-context", "min-length" => 1L, "max-length" => 2147483647L, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "no-services" }, ... }
According to documentation [1] if attribute is marked as "restart-required" => "no-services" no restart of service is necessary
no-services – Applying the operation to the runtime does not require the restart of any services. This value is the default if the restart-required descriptor is not present.
[1] https://docs.jboss.org/author/display/WFLY10/Description+of+the+Management+Model
- clones
-
JBEAP-9307 Changing Elytron default-authentication-context ends in reload-required state
- Closed