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
Hi Keith,
thanks for explanation.
It will be great if you can post skeletal code of ACL module.
Tomas
Keith Wall wrote
> Hi Tomas
>
> Unfortunately, Broker-J's access_control plugin is not too good. It
> is something we would like to rework when schedules allow. The
> current module
Hi Chuck,
Posted to the dev group but as well, but thought it might be worthwhile to
post here as well:
Have a couple of questions wrt QPID-7926
Question 1: what is the relevance of the is_pod<> result?
JIRA- 7926 (https://issues.apache.org/jira/browse/QPID-7926) states that:
"In a stand-alone
Hi Tomas
Unfortunately, Broker-J's access_control plugin is not too good. It
is something we would like to rework when schedules allow. The
current module actually uses an object modal that pre-dates the
current one - which leads to user confusion and an ugly adaption layer
in the code. 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.
> 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.
>
There is a cyrus-sal-ldap library that is available and
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
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
On Fri, Apr 6, 2018 at 10:21 AM, Michiel Lange wrote:
> Im sorry, I edited that one via the Nabble forums, but it seems tags
> don't get processed that well.
>
> So here it is again:
>
> thanks; that helps alot already... Once I get this running, I'll try and
> see how I can
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
Im sorry, I edited that one via the Nabble forums, but it seems tags
don't get processed that well.
So here it is again:
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
2018-04-06 11:57 GMT-04:00 Michiel Lange :
> I think I would not really mind either way (yet); Since on broker level
> one could/would set some policies, it would be logical to have the
> authorization remain on the broker;
>
Jiust FYI, you could set policies on the router as well
I think I would not really mind either way (yet); Since on broker level one
could/would set some policies, it would be logical to have the authorization
remain on the broker;
So, if qpid dispatch is unaware of credentials used (but passes those along)
might make matters a bit easier.
13 matches
Mail list logo