[
https://issues.apache.org/activemq/browse/SM-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen resolved SM-1915.
---------------------------------
Resolution: Fixed
The basic JMX authorization policy fix has been applied:
- in http://svn.apache.org/viewvc?view=revision&revision=880669 for the 3.3.x
trunk
- in http://svn.apache.org/viewvc?view=revision&revision=880679 for the 3.2.x
branch
Based on Claus' suggestions, I have raised SMX4-433 to look into creating a
more integrated solution for ServiceMix 4.x
> Support more fine-grained authorization on JMX access
> -----------------------------------------------------
>
> Key: SM-1915
> URL: https://issues.apache.org/activemq/browse/SM-1915
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-core
> Affects Versions: 3.2.3, 3.3.1
> Reporter: Gert Vanthienen
> Assignee: Gert Vanthienen
> Fix For: 3.2.4, 3.3.2
>
> Attachments: SM-1915.diff
>
>
> Currently, access to the JMX console access is being controlled by a JAAS
> login module. Once logged in to the JMX console, every user is allowed to do
> anything with the provided MBeans.
> This issue aims to add support for basic authorization control as well as
> provide a hook for implementing more fine-grained authorization schemes. The
> basic scheme should allow 'admin' users to do anything and limit the normal
> users to read-only operations.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
