« Return to Thread: [jira] [Created] (DERBY-5637) Document Derby's JMX capabilities and how to disable them

[jira] [Commented] (DERBY-5637) Document Derby's JMX capabilities and how to disable them

by JIRA jira@apache.org :: Rate this Message:

| View in Thread


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

Kim Haase commented on DERBY-5637:
----------------------------------

Should I also add the material in http://wiki.apache.org/db-derby/JMXSecurityExpectations? It's referenced from http://wiki.apache.org/db-derby/DerbyJMXQuickStart#Fine-grained_authorization:_Security_policy. However, it's full of warnings about being possibly outdated. I could put the material in and let you fix it ...

               

> Document Derby's JMX capabilities and how to disable them
> ---------------------------------------------------------
>
>                 Key: DERBY-5637
>                 URL: https://issues.apache.org/jira/browse/DERBY-5637
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation, JMX
>    Affects Versions: 10.9.0.0
>            Reporter: Rick Hillegas
>            Assignee: Kim Haase
>
> Derby's JMX beans are useful, although limited. We should document their capabilities as well as how to disable/restrict access to them in security-conscious environments.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

 « Return to Thread: [jira] [Created] (DERBY-5637) Document Derby's JMX capabilities and how to disable them