[ 
https://issues.apache.org/jira/browse/KARAF-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13802684#comment-13802684
 ] 

Christian Schneider edited comment on KARAF-2506 at 10/23/13 7:59 AM:
----------------------------------------------------------------------

If we can detect that the jmx connect uses the JConsole local connect feature 
we could assume the user has the admin role.
This kind of connect only works if Jconsole is started from the same user that 
started karaf. So this user has access to the karaf configs anyway. So the 
question is only if we can securely determine the connect is a local one.


was (Author: ch...@die-schneider.net):
If we can detect that the jmx connect uses the JConsole local connect feature 
we could assume the user has the admin role.
This kind of connect only works if Jconsole is started from the same user that 
started karaf. So this user has access to the karaf configs anyway.

> MBeans attributes are "unavailable"
> -----------------------------------
>
>                 Key: KARAF-2506
>                 URL: https://issues.apache.org/jira/browse/KARAF-2506
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-core
>    Affects Versions: 3.0.0
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Jean-Baptiste Onofré
>            Priority: Blocker
>             Fix For: 3.0.0
>
>
> Running Karaf 3.0.0-SNAPSHOT (trunk), and connecting jconsole, all Karaf 
> MBeans attributes are displayed as "unavailable" in red.
> It's the case for:
> - bundles in org.apache.karaf:type=bundle
> - configs in org.apache.karaf:type=config
> - features and repositories in org.apache.karaf:type=feature
> - instances in org.apache.karaf:type=instances
> - kars in org.apache.karaf:type=kar
> - level in org.apache.karaf:type=log
> - exports and imports in org.apache.karaf:type=package
> - services in org.apache.karaf:type=service
> - all attributes in org.apache.karaf:type=system
> I'm checking if it's not some ACLs missing (as the JMX ACL check attributes 
> using some operations name like get/set/is).



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to