[
https://issues.apache.org/jira/browse/ARTEMIS-3062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17264308#comment-17264308
]
Gary Tully commented on ARTEMIS-3062:
-------------------------------------
to have the command do it, would require a second parameter, I don't think we
can have a sensible default when the host is not a valid client address or
needs to use CIDR format. The intent was to lock down jolokia by default, but
it was a short cut to reuse the http-host parameter in this case. my bad!
> Incorrect Jolokia access config when using 0.0.0.0 http-host
> ------------------------------------------------------------
>
> Key: ARTEMIS-3062
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3062
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Priority: Major
>
> I downloaded Apache Artemis 2.16.0 from the official site and created an
> instance with command {{artemis create --http-host 0.0.0.0 --user default
> --password --default -- /var/lib/artemis}}.
> I set {{http-host}} to {{0.0.0.0}}, to let me access the management console
> from any address. This lets me access the console, but the configuration is
> wrong, since it sets the {{jolokia-access.xml:restrict.cors.allow-origin}} to
> {{\*://0.0.0.0*}}, which means that even though I can technically access the
> console, I get no data, just a mostly empty screen.
> I can, by hand, edit the file attribute to {{\*://*}}, but I'd prefer having
> the command do this to me instead. Is it a bug in the instance generator, or
> am I missing something?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
