[
https://issues.apache.org/jira/browse/ARTEMIS-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17332740#comment-17332740
]
Andrey Danilenko commented on ARTEMIS-3267:
-------------------------------------------
Thank you for your attention to my issue. I'm really trying to accommodate
messaging REST interface. The reason is that i have to integrate legacy
application worked out on the basis of a proprietary database with some new
application, exactly to export data from one to the other. These systems must
remain loosely coupled, thus message broker is the preferred tool especially
because the second one already uses Artemis. On the other hand database has
ready toolkit to interact via http, thus it was an obvious idea to configure in
this way: _Old application -> (http) -> Artemis -> (jms) -> New application_.
Maybe I didn't put in enough efforts to make _in-vm_ connection work, but now
artemis rest engine interacts with broker by _tcp_ only and this is news for me
about limitation on protocol for rest messaging.
> 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)
