This content has been marked as final.
Show 3 replies
-
1. Re: MBean jboss.as vanished after migration from Wildfly-10 to Wildfly-12
ehugonnet May 4, 2018 7:28 AM (in response to gjaekel)What happens if you don't use RBAC but simple for access-control ?
-
2. Re: MBean jboss.as vanished after migration from Wildfly-10 to Wildfly-12
gjaekel May 4, 2018 7:37 AM (in response to ehugonnet)A quick test -- just changing the attribute in the config -- shows that this trigger the issue!
-
3. Re: MBean jboss.as vanished after migration from Wildfly-10 to Wildfly-12
gjaekel May 7, 2018 5:53 AM (in response to gjaekel)So this is a bug? Is it reflated / corresponding to
- https://issues.jboss.org/browse/WFCORE-2061
- [JBEAP-13844] [GSS](7.1.z) Can not get core MBeans such as jboss.as and jboss.as.expr from application on EAP when RBAC …
- [JBEAP-13845] [GSS](7.2.0) Can not get core MBeans such as jboss.as and jboss.as.expr from application on EAP when RBAC …
The JBEAP-Issues mention a strange workaround: Adding the User "anonymous" to the rule Monitor will make the MBeans appear!
<access-control provider="rbac"> <role-mapping> <role name="SuperUser"> <include> <user name="$local"/> <user name="wild"/> <user name="root"/> <user name="admin"/> </include> </role> <role name="Monitor"> <include> <user name="dnb"/> <user name="anonymous"/> <--- this will work around the issue and make the MBean appear again! </include> </role> </role-mapping> </access-control>
This User is not need to inclueded in the mgmt-users.properties or mgmt-groups.properties files!