[
https://issues.apache.org/activemq/browse/AMQ-795?page=comments#action_37540 ]
Jonas Lim commented on AMQ-795:
-------------------------------
For this plugin we can just have a specific admin role (ie. tempAdmin) for
the temporary destinations. Then we can grant by default everyone admin roles
for temp destinations and still be able to remove them for certain users.
Since temp destination names are generated at runtime we'll need an approach
so we can map all temp destinations to a specific role.
I was thinking of just adding a setter method inside the authorizationMap to
set the authorizationentry for temporary destinations :
ie. .....
<authorizationMap>
<authorizationEntries>
<authorizationEntry queue="QUEUE.USERS.>" "read="admins"
write="admins" admin="admins"/>
<authorizationEntry topic="TOPIC.USERS.>" read="admins"
write="admins" admin="admins" />
</authorizationEntries>
<tempAuthorizationEntry tempAdmin="tempAdmins" />
</authorizationMap>\
.......
> security plugin to deal with temporary queue and topics better
> --------------------------------------------------------------
>
> Key: AMQ-795
> URL: https://issues.apache.org/activemq/browse/AMQ-795
> Project: ActiveMQ
> Issue Type: Improvement
> Reporter: james strachan
> Assigned To: Jonas Lim
> Fix For: 4.2.0
>
>
> Allow a role to be specified for read/write/admin of temporary queue and
> temporary topics
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
