-
Bug
-
Resolution: Won't Do
-
Major
-
None
-
7.1.0.DR7
When updating elytron resources, server ends up in reload-required state. For example
[standalone@localhost:9990 /] /subsystem=elytron/kerberos-security-factory=krbSF:write-attribute(name=debug, value=true) { "outcome" => "success", "response-headers" => { "operation-requires-reload" => true, "process-state" => "reload-required" } }
Make it possible for all (most - some may be impossible) resources to support runtime updates.
- incorporates
-
JBEAP-6490 Updating of elytron kerberos security factory requires reload
- Closed
- is cloned by
-
WFCORE-2423 Elytron resources runtime updates without reload
- Resolved
- is related to
-
JBEAP-6939 Elytron allow-resource-service-restart=true handling
- Closed
- relates to
-
JBEAP-10168 UnsupportedOperationException for {allow-resource-service-restart=true} for many attributes in Elytron subsystem
- Closed
-
JBEAP-10741 Elytron Keystore resource needs restart when is changed credential-reference attribute but restart-required is set to "no-services"
- Closed
-
JBEAP-10747 EAP server must be reloaded when is updated credential reference of credential store. There isn't any information that it needs reload.
- Closed