MDBs cannot be assigned a security-domain as there is no caller identity to authenticate. Override the security-domain to null in the MDB container configuration, or write a custom interceptor that takes the authentication information from the JMS message, or pull out the SecurityInterceptor from the MDB container configuration in standardjboss.xml. The latter will be the default in the final 3.0 release.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Stephen Coy" <[EMAIL PROTECTED]> To: "jboss-user" <[EMAIL PROTECTED]> Sent: Wednesday, May 29, 2002 5:11 PM Subject: [JBoss-user] Security and Message Driven Beans > Hi, > > > I am using JBoss 3.0RC3. > > I've got a stateful session bean which is associated with a Principal > that has been authenticated in our application's security domain. When I > try to send a message to a queue based MDB, I get the following > exception: > _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
