Thanks, I had a look at SASL External before, but Artemis doesn't support it
at the moment. Are there any plans for the future?
Unfortunately, the 2-way SSL solution isn't sufficient for our use-case. The
list of trusted clients is dynamic, and we want to be able to attach the
client certificate's
We have a custom login module that uses client certificates for
authentication (similar to CertificateLoginModule), but that doesn't seem to
support AMQP clients.
Looks like SASL PLAIN doesn't properly map to the Artemis' JAAS
implementation (doesn't propagate the connection so certificates can't
So I had a look at qpid-dispatch, but it doesn't seem to solve our problem.
Unless I'm misunderstanding, the way it works is that a client
(consumer/producer) connects to the router, which then links it to another
endpoint – a queue inside a broker, or producer/consumer. In our scenario we
want som
Thanks guys. Yes I meant that the bridge should use AMQP protocol and act as
an AMQP client from the target's perspective.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Artemis-AMQP-bridges-tp4728934p4729002.html
Sent from the ActiveMQ - User mailing list archive at Nab
Thanks, I'll have a look at Dispatch.
The use-case is a distributed ledger platform, where we have a peer-to-peer
network of nodes operated by different parties. Each node runs an Artemis
broker, and maintains queues for messages to other nodes, which get
forwarded using core bridges. We'd like to
In our setup we have multiple independent Artemis brokers, linked together by
core bridges to form a peer-to-peer network. We'd like to ensure that the
wire-level protocol used is always AMQP (1.0), but the core bridges seem to
only support core (which makes sense) and perform message conversion.
