You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Jiri Daněk (JIRA)" <ji...@apache.org> on 2017/10/05 11:16:01 UTC

[jira] [Commented] (ARTEMIS-1435) Expose the Jolokia security configuration for the web console

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

Jiri Daněk commented on ARTEMIS-1435:
-------------------------------------

[~gtully] This has the unfortunate result that when my machine has multiple names, in my case 127.0.0.1, localhost, and hugacaka, which is the hostname, I am able to access hawtio only on http://127.0.0.1:8161. On the other addresses, I get error toasts

{noformat}
[Core] Operation unknown failed due to: java.lang.Exception : Origin http://hugacaka:8161 is not allowed to call this agent

[Window] Uncaught TypeError: Cannot read property 'apply' of undefined (http://nixos:8161/console/app/app.js?0aab0bf03f0d4174:16:13975)
{noformat}

These other names resolve to 127.0.0.1.

How can I configure it for the other names, without having to list them all?

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