[
https://issues.apache.org/jira/browse/ARTEMIS-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17332445#comment-17332445
]
Justin Bertram commented on ARTEMIS-3267:
-----------------------------------------
[~kmursk], this is a known limitation with the REST interface. Currently it's
only suitable to be used with an in-vm connection to a broker in the same JVM.
It's worth noting that using the REST messaging interface usually isn't the
best idea for the following reasons:
# It is specific to ActiveMQ Artemis. Any applications that are written to use
it cannot be ported to any other broker. There is no standard which governs the
behavior of the interface.
# In almost every circumstance where REST makes sense the [STOMP
protocol|https://activemq.apache.org/components/artemis/documentation/latest/stomp.html]
is superior.
What's your use-case and why have you chosen to use the REST interface?
> REST API has no params for authentication in broker
> ---------------------------------------------------
>
> Key: ARTEMIS-3267
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3267
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: API
> Reporter: Andrey Danilenko
> Priority: Major
>
> Starting web application with rest api ends up with error _AMQ229031: Unable
> to validate user from . Username: null,_ if option *--allow-anonymous=Y* not
> applied while creating artemis instance. Because there is no way to pass
> authentication parameters via {{_<rest-messaging><url>_}} - only protocol,
> host and port are being parsed. Anonymous connections are not allowed for
> commercial operation. How to solve this ?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
