-
Bug
-
Resolution: Done
-
Major
-
10.1.0.Final
-
None
Analyzing the lists of boot ops from the core and minimalistic configs, I've identified differences in the following operations.
These operations are executed when the minimalistic config is loaded:
/core-service=management/security-realm=ManagementRealm:add # map-groups-to-roles is true by default /socket-binding-group=standard-sockets/socket-binding=management-http:add(interface="management",port="9990") /socket-binding-group=standard-sockets/socket-binding=management-native:add(interface="management",port="\${jboss.management.native.port:9999}") /core-service=management/management-interface=http-interface:add(console-enabled="false",security-realm="ManagementRealm",http-upgrade={"enabled" => true},socket-binding="management-http") /core-service=management/management-interface=native-interface:add(security-realm="ManagementRealm",socket-binding="management-native") # UNIQUE /socket-binding-group=standard-sockets:add(default-interface="public")
These operations are executed as part of the default core config:
/core-service=management/security-realm=ManagementRealm:add(map-groups-to-roles="false") /socket-binding-group=standard-sockets/socket-binding=management-http:add(interface="management",port="\${jboss.management.http.port:9990}") # accepts system prop /socket-binding-group=standard-sockets/socket-binding=management-https:add(interface="management",port="\${jboss.management.https.port:9993}") # https instead of native /core-service=management/management-interface=http-interface:add(security-realm="ManagementRealm",http-upgrade={"enabled" => true},socket-binding="management-http") # console-enabled is true by default /socket-binding-group=standard-sockets:add(default-interface="public",port-offset="\${jboss.socket.binding.port-offset:0}") # accepts system prop
- is cloned by
-
-
- Verified
-
