You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Domenico Francesco Bruscino (Jira)" <ji...@apache.org> on 2021/01/12 16:53:00 UTC

[jira] [Comment Edited] (ARTEMIS-3062) Incorrect Jolokia access config when using 0.0.0.0 http-host

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

Domenico Francesco Bruscino edited comment on ARTEMIS-3062 at 1/12/21, 4:52 PM:
--------------------------------------------------------------------------------

I see your point. I have just one concern on allowing any origin. Maybe we could warn the user on creating the broker instance in this special case.


was (Author: brusdev):
I see your point. I have just one concern on allow any origin. Maybe we could warn the user on creating the broker instance in this special case.

> 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)