[
https://issues.apache.org/jira/browse/ARTEMIS-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16192774#comment-16192774
]
Gary Tully commented on ARTEMIS-1435:
-------------------------------------
[~jdanek] i would replace "unfortunate" with "intentional".
If that bit of config that restricts access to those listed is removed, then
there is no restriction. Otherwise it needs a list or a selective wildcard
match.
see doc at: https://jolokia.org/reference/html/security.html#d0e2946
> Expose the Jolokia security configuration for the web console
> -------------------------------------------------------------
>
> Key: ARTEMIS-1435
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1435
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Web Console
> Affects Versions: 2.3.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Fix For: 2.4.0
>
>
> Jolokia JMX-HTTP bridge has advanced security features that are configured
> via a policy file. We should provide a template policy file in our
> configuration for easy access and to lock down the web console to ${http.host}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
