How do I configure an MDB so its driving Queue or Topic has security on it?
e.g. if I give role R read access to the Queue or Topic, I would expect the MDB to be able to access it if I specifed role R in its ejb-jar.xml as:
<security-identity><run-as><role-name>R</role-name></run-as></security-identity>
but I get an error when I deploy the MDB saying "not authorized to connect to the destination"
Why you want to secure the access of a MDB to a destination?
There isn't a security problem because access should be checked when the message producer access a destination to send a message.
Have fun - Andy