Description of problem: Disabling the web interface of the admin console using the console-enabled attribute does not work in domain mode. Version-Release number of selected component (if applicable): EAP 6.3.3 How reproducible: Very Steps to Reproduce: 1. Set up domain installation 2. Set console-enabled="false" attribute on http management interface in host.xml [1] or using CLI [2] 3. Log into admin console ( http://localhost:9990/console ) [1] Set console-enabled in host.xml: <http-interface security-realm="ManagementRealm" console-enabled="false"> <socket interface="management" port="${jboss.management.http.port:9990}" secure-port="9443"/> </http-interface> [2] Set console-enabled through CLI: /host=master/core-service=management/management-interface=http-interface/:write-attribute(name=console-enabled,value=false) Actual results: Able to access and log into web admin console. Expected results: Empty or no page is displayed as in standalone mode. Additional info:
I just added docs text, written as if this were already fixed. It's not, but it's easy. The org.jboss.as.host.controller.operations.HttpManagementAddHandler class should be more like the org.jboss.as.server.operations.HttpManagementAddHandler class, and handle this attribute. Note the server class isn't perfect either as it does this: boolean consoleEnabled = model.get(ModelDescriptionConstants.CONSOLE_ENABLED).asBoolean(true); instead of using the correct idiom and delegating to the AttributeDefinition: boolean consoleEnabled = CONSOLE_ENABLED.resolveModelAttribute(console, model).asBoolean(); That flaw doesn't harm anything, but might as well correct it.
Fix pending merge: WFCORE-678
Verified for EAP 6.4.2.CP.CR1.
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.