[
https://issues.apache.org/jira/browse/AMQ-5654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Geert Pante updated AMQ-5654:
-----------------------------
Description:
Currently, for REST or Ajax clients to connect to a secured ActiveMQ, the
client side needs to send the activemq credentials over HTTP.
It should be possible to use a different authentication mechanism for the HTTP
connection, and let the servlet use a system account to connect to ActiveMQ.
Additionally, it would be great to allow ${} placeholders in the servlet
context parameters, which could be resolved by system properties.
was:
Currently, for REST or Ajax clients to connect to a secured ActiveMQ, the
client side needs to send the activemq credentials over HTTP.
It should be possible to use a different authentication mechanism for the HTTP
connection, and let the servlet use a system account to connect to ActiveMQ.
Affects Version/s: 5.11.1
> Allow ActiveMQ authentication on server side for REST/Ajax clients.
> -------------------------------------------------------------------
>
> Key: AMQ-5654
> URL: https://issues.apache.org/jira/browse/AMQ-5654
> Project: ActiveMQ
> Issue Type: Improvement
> Affects Versions: 5.9.1, 5.11.1
> Reporter: Geert Pante
>
> Currently, for REST or Ajax clients to connect to a secured ActiveMQ, the
> client side needs to send the activemq credentials over HTTP.
> It should be possible to use a different authentication mechanism for the
> HTTP connection, and let the servlet use a system account to connect to
> ActiveMQ.
> Additionally, it would be great to allow ${} placeholders in the servlet
> context parameters, which could be resolved by system properties.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
