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
>> > doesn't look like it is using TLS, let alone
On Mon, Apr 16, 2018 at 10:08 AM, 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
> > doesn't look like it is using TLS, let alone supplying a client cert.
> > Are
> 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
On 16/04/18 12:21, mlange wrote:
But then I looked in the broker log... and there it is:
2018-04-16 13:05:04,657 WARN
[org.apache.activemq.artemis.protocol.amqp.proton.handler.ProtonHandler]
AMQ119031: Unable to validate user from /192.168.0.1:33034. Username: null;
SSL certificate subject DN:
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
On Wed, Apr 11, 2018 at 10:32 AM, mlange wrote:
> 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
>
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
On Tue, Apr 10, 2018 at 10:58 AM, mlange wrote:
> 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
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.
On Mon, Apr 9, 2018 at 9:52 AM, mlange wrote:
> 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
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,
erzonden: vrijdag 6 april 2018 17:14
> Aan: users@qpid.apache.org
> Onderwerp: Re: Qpid Dispatch authenticate through ldap, is this possible
>
> 2018-04-06 9:22 GMT-04:00 Michiel Lange:
>
> > Hi,
> >
> > I use Qpid Dispatch to route JMS to an Artemis broker, which
.
-Oorspronkelijk bericht-
Van: Ganesh Murthy
Verzonden: vrijdag 6 april 2018 17:14
Aan: users@qpid.apache.org
Onderwerp: Re: Qpid Dispatch authenticate through ldap, is this possible
2018-04-06 9:22 GMT-04:00 Michiel Lange:
> Hi,
>
> I use Qpid Dispatch to route JMS to an Artemis broker
2018-04-06 9:22 GMT-04:00 Michiel Lange :
> Hi,
>
> I use Qpid Dispatch to route JMS to an Artemis broker, which I have
> configured to use LDAP; allowing certain groups to create queues, send
> messages or receive.
> I am strugging getting Qpid dispatch to even use
2018-04-06 9:22 GMT-04:00 Michiel Lange :
> Hi,
>
> I use Qpid Dispatch to route JMS to an Artemis broker, which I have
> configured to use LDAP; allowing certain groups to create queues, send
> messages or receive.
> I am strugging getting Qpid dispatch to even use
Michiel,
There is some newer documentation on setting up authentication and
authorization, but it hasn't been published on the site yet. For now, you
can see it here:
https://github.com/apache/qpid-dispatch/blob/master/doc/new-book/configuration-security.adoc
If that doesn't help, or if you see
; brokerpair, rather than the bunch I had defined, it breaks the purpose here
> :-) )
>
> As you can see, I have set everything, except the connection to the broker
> to ANONYMOUS; This because I have the broker configured to require login.
>
>
> -Oorspronkelijk bericht-
>
uire login.
-Oorspronkelijk bericht-
Van: mlange [mailto:mla...@anwb.nl]
Verzonden: vrijdag 6 april 2018 16:19
Aan: users@qpid.apache.org
Onderwerp: Re: Qpid Dispatch authenticate through ldap, is this possible
thanks; that helps alot already... Once I get this running, I'll try and see
how I can
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
2018-04-06 9:22 GMT-04:00 Michiel Lange :
> Hi,
>
> I use Qpid Dispatch to route JMS to an Artemis broker, which I have
> configured to use LDAP; allowing certain groups to create queues, send
> messages or receive.
>
There is a cyrus-sal-ldap library that is available and
Hi,
I use Qpid Dispatch to route JMS to an Artemis broker, which I have configured
to use LDAP; allowing certain groups to create queues, send messages or receive.
I am strugging getting Qpid dispatch to even use authentication, leave alone if
the authentication information would be stored in
22 matches
Mail list logo