"timfox" wrote : When you say "access" do you mean send messages to, or consume messages from? I have only tried consuming, but I don't have any reason to believe that sending would be different. Using SecurityTest settings, for example, if I login as user guest, and call createTemporaryQueue, the queue has default permissions requiring role "def" to read/write to it (verified under a debugger). User guest doesn't have role "def". "timfox" wrote : anonymous wrote : 2) Disallow creating temporary destinations that the logged-in user will not be able to use - doesn't solve the actual problem. | | | | Which user are you referring to? The creator of the temp destination, or the consumer? The creator. "timfox" wrote : anonymous wrote : | | 3) Have some configuration mechanism for temporary destination permissions - not sure where it would go, to make it sufficiently flexible. | | | | Temp destination security could be overridden in the connection factory. That's where the other temp destination attributes are overridden. But this means that different users will all use the same temp destination security? Is this ok? Shouldn't the temp destination permissions be configurable on a per-user basis? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055569#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...