Ganesh Murthy wrote
> On Mon, Apr 16, 2018 at 10:08 AM, mlange
> mlange@
> wrote:
>
>>
>> > That looks a bit as if artemis is trying to authenticate the connection
>> > via a client certificate. From the config snippet you supplied it
>> >
Done: https://issues.apache.org/jira/browse/DISPATCH-968
--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html
-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands,
> That looks a bit as if artemis is trying to authenticate the connection
> via a client certificate. From the config snippet you supplied it
> doesn't look like it is using TLS, let alone supplying a client cert.
> Are you able to get a protocol trace for the interaction between the
> router and
aconway.rh wrote
> On Mon, Apr 16, 2018 at 8:52 AM, Gordon Sim
> gsim@
> wrote:
>
>
>>
>> No. The problem is that a transaction could involve messages to/from
>> different brokers, i.e. the transaction would become a distributed
>> transaction. At present there is no support for that in the
Hi all,
QDR has some limited support for transactions, seeing a special endpoint
$coordinator.
When one has QDR with only one broker behind it you can do a
linkRoute {
prefix: $coordinator
dir: in
conn: broker1
}
and the same, but then dir: out
However, this will work for one broker.
So, now I have QDR able to authenticate via LDAP via SASL; When running some
tests, I got some errors that I could not relate... MessageProducer is
closed as IllegalStateException; Didn't have a clue...
But then I looked in the broker log... and there it is:
2018-04-16 13:05:04,657 WARN
Ganesh Murthy wrote
> If I am reading this correctly, you were able to get LDAP to work on the
> router after installing the correct rpms on CentOS? Congratulations.
> Share your steps so I can try this locally.
>
> Thanks.
I am and I have!
For the RPM: search on rpmfind.net to
Thanks for that one; seems like a pretty complex way to get things done. In
the mean time I found an rpm for CentOS 7, installed it and went a bit
around things; when I can reproduce what I did (and leave out all the wrong
steps in between)
It would then be a good idea to compare both solutions
Ganesh Murthy wrote
> This seems to be very similar to the problem I ran into while trying to
> setup LDAP. (I assume you have the latest cyrus-sasl-ldap library
> installed)
> Your configs look good. One thing you can do is to look at syslog output
> and see the error messages from cyrus-sasl.
I went on and got a bit further, was hoping "to be there" though. Yet, no
luck.
So far, what I've been able to gather from around the interwebs, along with
the new documentation (which is a huge step forward compared to the older
documentation):
I have configured openldap to use SASL (saslHost,
thanks; that helps alot already... Once I get this running, I'll try and see
how I can contribute to the documentation, which I find a bit lacking in
this respect.
I have it running with saslMechanism ANONYMOUS, however, I'd like the
dispatch router to "pass through" the credentials to the
11 matches
Mail list logo
