[
https://issues.apache.org/jira/browse/AMQ-6908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16976654#comment-16976654
]
ASF subversion and git services commented on AMQ-6908:
------------------------------------------------------
Commit e7b7334e42d8709fdf69e5c8d929f6ad25dd27ec in activemq's branch
refs/heads/master from Alvin Lin
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=e7b7334 ]
AMQ-6908 allow use of ActiveMQ console login credential (for authorization)
when browsing messages through the console
(cherry picked from commit 822cf6203437f06a58e8e442de87b8416ad232e6)
> Inconsistent authorization in web console
> -----------------------------------------
>
> Key: AMQ-6908
> URL: https://issues.apache.org/jira/browse/AMQ-6908
> Project: ActiveMQ
> Issue Type: Bug
> Components: Web Console
> Affects Versions: 5.15.0, 5.15.1, 5.15.2, 5.15.3
> Reporter: Alvin Lin
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Fix For: 5.16.0, 5.15.11
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Looking at org.apache.activemq.web.WebClient#createWebClient we can actually
> configure the connectionFactory in webconsle-embedded.xml to use the
> credential in the HTTP Authorization header to connect to the core ActiveMQ
> broker by setting the username and password to null.
> But when I do that, the browse in console feature stops working if I have
> authentication enabled, because org.apache.activemq.web.QueueBrowseQuery
> requires the given connectionFactory to be configured with non-null username
> and password.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
