Meaningless Drivel is fun!
The moose likes JBoss/WildFly and the fly likes Securing JMS Destinations Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » JBoss/WildFly
Bookmark "Securing JMS Destinations" Watch "Securing JMS Destinations" New topic

Securing JMS Destinations


Joined: Jan 30, 2005
Posts: 3
I have a problem in configuring the security for the destination queue which is the permanent queue. I have DBServerLogin configured for "jbossmq" in login-config.xml where unauthenticated identity is "guest"
I dont want to add this principal to my SecurityConfig for the queue. If I dont add the principal I get
javax.jms.JMSSecurityException: Connection not authorized to add messages to destination: FirstQueue while trying to send messages to this queue from jms client.

Joined: Jan 30, 2005
Posts: 3
Suppose somebody is using jms app. client for adding messages to queue while MDB is the consumer.
a)app client should supply username,password while getting queueConnection using myConnectionFactory.createQueueConnection("username","passwd")
b)MDB deployment on the otherhand should be mentioning these in jboss-jar.xml.

<mdb-passwd >dynsub</mdb-passwd>

[ February 01, 2005: Message edited by: M.Junaid ]
I agree. Here's the link:
subject: Securing JMS Destinations
It's not a secret anymore!