-
Bug
-
Resolution: Done
-
Blocker
-
7.1.0.DR9
-
None
A duplicate resource failure followed by removing filters attribute in /subsystem=elytron/mechanism-provider-filtering-sasl-server-factory=elytron and reload results in server boot failure.
15:50:29,961 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. 15:50:29,974 INFO [org.jboss.as] (MSC service thread 1-8) WFLYSRV0050: JBoss EAP 7.1.0.Alpha1 (WildFly Core 3.0.0.Alpha13-redhat-1) stopped in 7ms
Why it's a blocker?
- because the unsetting of the required attribute is allowed, customers can simply end up with dead EAP (by common sense they could expect that removing all filters mean allowing all SASL factories)
- it seems the first (failed) command doesn't do a correct clean up and it results in problems during subsequent CLI operations
- is cloned by
-
WFLY-7981 The server boot failure after unsetting the filter attribute in mechanism-provider-filtering-sasl-server-factory (Elytron)
- Closed
- is incorporated by
-
JBEAP-7248 Elytron mechanism-provider-filtering-sasl-server-factory cannot be added without filters attribute in CLI
- Closed
-
JBEAP-8449 Upgrade to Elytron Subsystem 1.0.0.Beta2
- Closed