Hi Keith,
excellent idea, this will completely solve our use case.
Regards,
Tomas
--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html
-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
Hi Tomas
Having had change to reflect on this a bit more, I am contemplating a
change to the existing access-control-plugin which would let you
express rules for objects that the current user has created using a
special pseudo subject 'OWNER'.
It will look something like:
ACL ALLOW-LOG OWNER
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 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
Hi,
I am trying to get working temporary queues on Java Broker. Each user should
have access only to queue which he created.
ACL rights:
ACL ALLOW-LOG user1 ACCESS VIRTUALHOST
ACL ALLOW-LOG user1 CREATE QUEUE temporary="true" owner="user1"
ACL ALLOW-LOG user1 CONSUME QUEUE temporary="true"
