Done.
The jbossmq security manager now accepts a default security
configuration attribute:
<mbean code="org.jboss.mq.security.SecurityManager"
name="jboss.mq:service=SecurityManager">
<attribute name="DefaultSecurityConfig">
<security>
<role name="guest" read="true" write="true" create="true"/>
</security>
</attribute>
<depends
optional-attribute-name="NextInterceptor">jboss.mq:service=DestinationManager</depends>
</mbean>
Regards,
Adrian
On Fri, 2003-08-01 at 06:44, Scott M Stark wrote:
> The default security metadata is to allow the 'guest' role read, write
> and create permissions so the user that you pass to createQueueConnection
> must has the 'guest' role. We need to add the ability to define the security
> settings of the temporary destinations though.
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
