Index: lams_build/conf/unix/jboss/login-config.xml
===================================================================
RCS file: /usr/local/cvsroot/lams_build/conf/unix/jboss/login-config.xml,v
diff -u -r1.1 -r1.2
--- lams_build/conf/unix/jboss/login-config.xml	4 May 2005 00:25:06 -0000	1.1
+++ lams_build/conf/unix/jboss/login-config.xml	5 Sep 2005 06:58:01 -0000	1.2
@@ -51,6 +51,18 @@
        </authentication>
     </application-policy>
 
+    <!-- Security domain for JBossMQ when using file-state-service.xml
+    <application-policy name = "jbossmq">
+       <authentication>
+          <login-module code = "org.jboss.mq.sm.file.DynamicLoginModule"
+             flag = "required">
+             <module-option name = "unauthenticatedIdentity">guest</module-option>
+             <module-option name = "sm.objectname">jboss.mq:service=StateManager</module-option>
+          </login-module>
+       </authentication>
+    </application-policy>
+    -->
+
     <!-- Security domains for testing new jca framework -->
     <application-policy name = "HsqlDbRealm">
        <authentication>
@@ -64,18 +76,6 @@
        </authentication>
     </application-policy>
 
-    <application-policy name = "FirebirdDBRealm">
-       <authentication>
-          <login-module code = "org.jboss.resource.security.ConfiguredIdentityLoginModule"
-             flag = "required">
-             <module-option name = "principal">sysdba</module-option>
-             <module-option name = "userName">sysdba</module-option>
-             <module-option name = "password">masterkey</module-option>
-             <module-option name = "managedConnectionFactoryName">jboss.jca:service=XaTxCM,name=FirebirdDS</module-option>
-          </login-module>
-       </authentication>
-    </application-policy>
-
     <application-policy name = "JmsXARealm">
        <authentication>
           <login-module code = "org.jboss.resource.security.ConfiguredIdentityLoginModule"
@@ -96,8 +96,8 @@
        <authentication>
           <login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule"
              flag = "required">
-             <module-option name="usersProperties">jmx-console-users.properties</module-option>
-             <module-option name="rolesProperties">jmx-console-roles.properties</module-option>
+           <module-option name="usersProperties">props/jmx-console-users.properties</module-option>
+           <module-option name="rolesProperties">props/jmx-console-roles.properties</module-option>
           </login-module>
        </authentication>
     </application-policy>
@@ -116,6 +116,19 @@
        </authentication>
     </application-policy>
 
+    <!-- A template configuration for the JBossWS web application (and transport layer!).
+      This defaults to the UsersRolesLoginModule the same as other and should be
+      changed to a stronger authentication mechanism as required.
+    -->
+    <application-policy name="JBossWS">
+      <authentication>
+        <login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule"
+          flag="required">
+          <module-option name="unauthenticatedIdentity">anonymous</module-option>
+        </login-module>
+      </authentication>
+    </application-policy>
+
     <!-- The default login configuration used by any security domain that
     does not have a application-policy entry with a matching name
     -->
@@ -137,7 +150,6 @@
        </authentication>
     </application-policy>
 
-
 	<application-policy name = "lams-DB">
        <authentication>
           <login-module code = "org.jboss.security.auth.spi.DatabaseServerLoginModule" flag = "required">