1 Reply Latest reply on Mar 31, 2005 9:20 PM by Scott Stark

    Setting jaas realm for jms destinations

    Gray Newbie


      This is a simple question I believe.


      How do I set a given jms destination to live in a jaas realm that is different from the default "jbossmq" realm?


      In my login-config.xml I have specified different realms "app1-jms", "app2-jms" etc since multiple ears can be deployed on one running app server instance and these could potentially have different security settings since they are written by different people.

      I have a file in my jboss server that is specific to a given app's jms requirements <server-directory>/deploy/jboss/app1-jms-destinations-service.xml that contains the following

      <?xml version="1.0" encoding="UTF-8"?>
       <mbean code="org.jboss.mq.server.jmx.Queue"
       <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
       <depends optional-attribute-name="SecurityManager">
       <attribute name="SecurityConf">
       <role name="guest" read="false" write="false" create="false"/>
       <role name="trader" read="true" write="true" create="false"/>
       <role name="noacc" read="false" write="false" create="false"/>

      What do I put in the above file to tell it to use the "app1-jms" jaas domain?

        • 1. Re: Setting jaas realm for jms destinations
          Scott Stark Master


           <mbean code="org.jboss.mq.security.SecurityManager" name="jboss.mq:service=SecurityManager">
           <attribute name="DefaultSecurityConfig">
           <role name="guest" read="true" write="true" create="true"/>
           <attribute name="SecurityDomain">java:/jaas/NOT-jbossmq</attribute>
           <depends optional-attribute-name="NextInterceptor">jboss.mq:service=DestinationManager</depends>