[JBoss Messaging] - Re: Secure Queue implementation in JBoss 4.0.2.GA
by mskonda
You can secure your destinations (topics/queues) either individually or on a global basis.
Individual security:
Add the 'SecurityConfig' attribute with appropriate role access as shown below to the individual destination configuration:
| <mbean code="org.jboss.jms.server.destination.TopicService"
| name="jboss.messaging.destination:service=Topic,name=mySecuredTopic"
| xmbean-dd="xmdesc/Topic-xmbean.xml">
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| <depends>jboss.messaging:service=PostOffice</depends>
|
| <attribute name="SecurityConfig">
| <security>
| <role name="jms_sub" read="true" write="false" create="false"/>
| <role name="jms_pub" read="false" write="true" create="false"/>
| <role name="jms_pubsub" read="true" write="true" create="false"/>
| <role name="jms_dursub" read="true" write="false" create="true"/>
| <role name="jms_admin" read="true" write="true" create="true"/>
| </security>
| </attribute>
| </mbean>
|
Of course, thsoe roles should be defined in your data store.
On a global basis, edit the deploy/jboss-messaging.sar/messaging-service.xml and add the 'DefaultSecurityConfig' block:
| <attribute name="DefaultSecurityConfig">
| <security>
| <role name="jms_sub" read="true" write="false" create="false"/>
| <role name="jms_pub" read="false" write="true" create="false"/>
| <role name="jms_pubsub" read="true" write="true" create="false"/>
| <role name="jms_dursub" read="true" write="false" create="true"/>
| <role name="jms_admin" read="true" write="true" create="true"/>
| </security>
| </attribute>
|
There's a detailed explanation on the user manual here.
http://labs.jboss.com/file-access/default/members/jbossmessaging/freezone...
/Madhu
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4122080#4122080
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4122080
18 years, 6 months
[JBoss jBPM] - Re: Strange Asynchronous Behaviour of JBPM(3.2.2)
by soumya_in
Yes...Asynchronous means a non-blocking.I have a requirement like this. e.g. CreditValidation.My main process validate a credit card no which will be validated in a subprocess.At that point customer registration will be done in the main process.Now at all a customer entered a wrong credit card no i.e. irrelevant to the customer registration process.Untill or unless a customer purchase for something,useful credit validation is not required.Now the scenario is looking bit difficult.Since to invoke a subprocess within a main process I used a process-state and made it asynch="true".
Now the two scenario is possible
1) I will use executionContext.getNode().leave(executionContext);
If I do this subprocess will not be invoked.Token traverses to the next activity of the main process.
2)If i do not do this all previous activities before process-state go blocking
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4122077#4122077
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4122077
18 years, 6 months