[
https://issues.apache.org/jira/browse/DERBY-3462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12584595#action_12584595
]
John H. Embretsen commented on DERBY-3462:
------------------------------------------
I'd like to mark DERBY-1387 (this issue's parent) as resolved for the 10.4
release. Code related to this issue has gone into both trunk and 10.4, but I
don't know if there are plans to do more. Should this issue be converted to a
standalone issue, or could it be considered resolved/fixed?
> Require new permissions in o.a.d.security.SystemPermission to allow control
> to Derby's JMX management and to ensure information is not leaked through JMX
> ---------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3462
> URL: https://issues.apache.org/jira/browse/DERBY-3462
> Project: Derby
> Issue Type: Sub-task
> Components: JMX, Security
> Reporter: Daniel John Debrunner
> Assignee: Daniel John Debrunner
> Priority: Minor
>
> Plan is to implement proposal defined in:
> http://wiki.apache.org/db-derby/JMXSecurityExpectations#head-de15a7e9d474784775933965fe963b6ac46e7ad0
> E.g.
> jmxControl for the ability to call the operations on ManagementMBean.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
