Red Hat Bugzilla – Bug 1019100
Definition of security constrain per Queue/Topic creation shouldn't be enforced
Last modified: 2014-01-02 15:38:38 EST
Description of problem:
When creating new Queue/Topic there is required to fill Security Configurations. It doesn't make sense to fill it on per Queue/Topic basis. Per discussion with our messaging guy, there is possible to define the permissions more globally.
Therefore this shouldn't be required only left as optional setting if needed to be set different for specific Queue/Topic
Version-Release number of selected component (if applicable):
JON 3.2.0.ER3 vs EAP 5.2.0
How reproducible: always
Steps to Reproduce:
1. import EAP 5 server
2. in server->JBoss Messaging->inventory->create child->Queue/Topic
3. one of required parts is to fill Security Configurations
The Security Configurations needs to be filled with at least two entries
Security Configurations shouldn't be required to be set
requirement to put at least two Security Configurations does make even less sense.
time: 2013-10-17 19:02:32 +0200
author: Jirka Kremser - firstname.lastname@example.org
message: [BZ 1019100] - Definition of security constrain per Queue/Topic creation
shouldn't be enforced - there is no need to require at least
two items of "Security Configurations". The security for
topics/queues can be set globally somewhere else or even turned off.
Moving to ON_QA for testing in the next build.
Verified in JON 3.2.0.ER4