[
https://issues.apache.org/jira/browse/ARTEMIS-2779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17115403#comment-17115403
]
Justin Bertram commented on ARTEMIS-2779:
-----------------------------------------
Artemis 2.11.0 uses Hawtio 1.5.5, but 2.12.0 uses 1.5.12. The upgrade was made
due to ARTEMIS-2606. Looking through the commit log (generated using {{git log
hawtio-1.5.5..hawtio-1.5.12}}) I see [this
commit|https://github.com/hawtio/hawtio/commit/5fcc8f5f155773d66d51882724d380ab12b80660]
which may have impacted this use-case.
In any event, you *must* pass the proper {{Origin}} header now. By default it
doesn't appear that {{curl}} passes this header which is why it doesn't work.
You could also get the same behavior as before by passing {{--relax-jolokia}}
when you create the broker as this will omit {{<strict-checking/>}} from
{{jolokia-access.xml}}.
> In Artemis >= 2.12.0 jolokia won't accept connections
> ------------------------------------------------------
>
> Key: ARTEMIS-2779
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2779
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.12.0, 2.13.0
> Environment: OS: Ubuntu 20.04 LTS x86_64
> Kernel: 5.4.0-29-generic
> Shell: bash 5.0.16
> Memory: 4385MiB / 32096MiB
>
> Reporter: Victor Romero
> Priority: Blocker
>
>
> In Artemis >= 2.12.0 jolokia won't accept connections, and will return the
> following:
> {quote}{"error_type":"java.lang.Exception","error":"java.lang.Exception :
> Origin null is not allowed to call this agent","status":403}
> {quote}
> Steps to reproduce:
> Create a vanilla 2.1[23]\{1}.0 broker instance with user admin password
> admin. Run it, and run the following command:
> {{curl -u admin:admin [http://localhost:8161/console/jolokia]}}
> I'm tagging as blocker as a broker without monitoring is IMHO more a problem
> than a solution, but feel free to change.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
