-
1. Re: testQueue not authorized to subscribe
joelvogt Jul 9, 2002 8:20 PM (in response to kevin7010)Can you post the code you are using to connect to the queue resource? I am guessing this will be the problem
-
2. Re: testQueue not authorized to subscribe
kevin7010 Jul 9, 2002 10:27 PM (in response to kevin7010)
<depends optional-attribute name="JBossMQService">jboss.mq:service=Server
<depends optional-attribute-name="SecurityManager">jboss.mq:service=SecurityManager
<application-policy name = "jbossmq">
<login-module code = "org.jboss.mq.sm.file.DynamicLoginModule"
flag = "required">
<module-option name = "unauthenticatedIdentity">guest</module-option>
<module-option name = "sm.objectnam">jboss.mq:service=StateManager</module-option>
</login-module>
</application-policy>
<application-policy name = "JmsXARealm">
<login-module code = "org.jboss.resource.security.ConfiguredIdentityLoginModule"
flag = "required">
<module-option name = "principal">guest</module-option>
<module-option name = "userName">guest</module-option>
<module-option name = "password">guest</module-option>
<module-option name = "managedConnectionFactoryName">jboss.jca:service=XaTxCM,name=jmsra</module-option>
</login-module>
</application-policy>
<message-driven>
<ejb-name>test/TestMessage</ejb-name>
<destination-jndi-name>queue/testQueue</destination-jndi-name>
</message-driven>
These are the config parameters which I think are important. I've looked at ra.xml in jms-ra.rar which doesn't actually specific a username or password value. Is that to left untouched? -
3. Re: testQueue not authorized to subscribe
kevin7010 Jul 9, 2002 10:31 PM (in response to kevin7010)
<depends optional-attribute name="JBossMQService">jboss.mq:service=Server
<depends optional-attribute-name="SecurityManager">jboss.mq:service=SecurityManager
<application-policy name = "jbossmq">
<login-module code = "org.jboss.mq.sm.file.DynamicLoginModule"
flag = "required">
<module-option name = "unauthenticatedIdentity">guest</module-option>
<module-option name = "sm.objectnam">jboss.mq:service=StateManager</module-option>
</login-module>
</application-policy>
<application-policy name = "JmsXARealm">
<login-module code = "org.jboss.resource.security.ConfiguredIdentityLoginModule"
flag = "required">
<module-option name = "principal">guest</module-option>
<module-option name = "userName">guest</module-option>
<module-option name = "password">guest</module-option>
<module-option name = "managedConnectionFactoryName">jboss.jca:service=XaTxCM,name=jmsra</module-option>
</login-module>
</application-policy>
<message-driven>
<ejb-name>test/TestMessage</ejb-name>
<destination-jndi-name>queue/testQueue</destination-jndi-name>
</message-driven>
These are the config parameters which I think are important. I've looked at ra.xml in jms-ra.rar which doesn't actually specific a username or password value. Is that to left untouched? -
4. Re: testQueue not authorized to subscribe
kevin7010 Jul 9, 2002 10:32 PM (in response to kevin7010)
<depends optional-attribute name="JBossMQService">jboss.mq:service=Server
<depends optional-attribute-name="SecurityManager">jboss.mq:service=SecurityManager
<application-policy name = "jbossmq">
<login-module code = "org.jboss.mq.sm.file.DynamicLoginModule"
flag = "required">
<module-option name = "unauthenticatedIdentity">guest</module-option>
<module-option name = "sm.objectnam">jboss.mq:service=StateManager</module-option>
</login-module>
</application-policy>
<application-policy name = "JmsXARealm">
<login-module code = "org.jboss.resource.security.ConfiguredIdentityLoginModule"
flag = "required">
<module-option name = "principal">guest</module-option>
<module-option name = "userName">guest</module-option>
<module-option name = "password">guest</module-option>
<module-option name = "managedConnectionFactoryName">jboss.jca:service=XaTxCM,name=jmsra</module-option>
</login-module>
</application-policy>
<message-driven>
<ejb-name>test/TestMessage</ejb-name>
<destination-jndi-name>queue/testQueue</destination-jndi-name>
</message-driven>
These are the config parameters which I think are important. I've looked at ra.xml in jms-ra.rar which doesn't actually specific a username or password value. Is that to left untouched? -
5. Re: testQueue not authorized to subscribe
kevin7010 Jul 9, 2002 10:33 PM (in response to kevin7010)
<depends optional-attribute name="JBossMQService">jboss.mq:service=Server
<depends optional-attribute-name="SecurityManager">jboss.mq:service=SecurityManager
<application-policy name = "jbossmq">
<login-module code = "org.jboss.mq.sm.file.DynamicLoginModule"
flag = "required">
<module-option name = "unauthenticatedIdentity">guest</module-option>
<module-option name = "sm.objectnam">jboss.mq:service=StateManager</module-option>
</login-module>
</application-policy>
<application-policy name = "JmsXARealm">
<login-module code = "org.jboss.resource.security.ConfiguredIdentityLoginModule"
flag = "required">
<module-option name = "principal">guest</module-option>
<module-option name = "userName">guest</module-option>
<module-option name = "password">guest</module-option>
<module-option name = "managedConnectionFactoryName">jboss.jca:service=XaTxCM,name=jmsra</module-option>
</login-module>
</application-policy>
<message-driven>
<ejb-name>test/TestMessage</ejb-name>
<destination-jndi-name>queue/testQueue</destination-jndi-name>
</message-driven>
These are the config parameters which I think are important. I've looked at ra.xml in jms-ra.rar which doesn't actually specific a username or password value. Is that to left untouched? -
6. Re: testQueue not authorized to subscribe
kevin7010 Jul 9, 2002 10:37 PM (in response to kevin7010)
<depends optional-attribute name="JBossMQService">jboss.mq:service=Server
<depends optional-attribute-name="SecurityManager">jboss.mq:service=SecurityManager
<application-policy name = "jbossmq">
<login-module code = "org.jboss.mq.sm.file.DynamicLoginModule"
flag = "required">
<module-option name = "unauthenticatedIdentity">guest</module-option>
<module-option name = "sm.objectnam">jboss.mq:service=StateManager</module-option>
</login-module>
</application-policy>
<application-policy name = "JmsXARealm">
<login-module code = "org.jboss.resource.security.ConfiguredIdentityLoginModule"
flag = "required">
<module-option name = "principal">guest</module-option>
<module-option name = "userName">guest</module-option>
<module-option name = "password">guest</module-option>
<module-option name = "managedConnectionFactoryName">jboss.jca:service=XaTxCM,name=jmsra</module-option>
</login-module>
</application-policy>
<message-driven>
<ejb-name>test/TestMessage</ejb-name>
<destination-jndi-name>queue/testQueue</destination-jndi-name>
</message-driven>
These are the config parameters which I think are important. I've looked at ra.xml in jms-ra.rar which doesn't actually specific a username or password value. Is that to left untouched?