&quot;anil.saldhana(a)jboss.com&quot; wrote : | Scott, I understand that the custom application policies are not being found, hence it is defaulting to "other". But what I do not understand is from where is the DynamicLoginConfigService kicking in, for this test case? It is neither explicitly defined in this test deployment nor anything is done from the test case. | | <local-tx-datasource> | <jndi-name>RunAsIdentityDS</jndi-name> | <connection-url>jdbc:hsqldb:mem:RunAsIdentityDB</connection-url> | <driver-class>org.hsqldb.jdbcDriver</driver-class> | <!-- The default login and password used for run-as --> | <user-name>sa</user-name> | <password></password> | <security-domain-and-application>RunAsIdentityDSRealm</security-domain-and-application> | <metadata> | <type-mapping>Hypersonic SQL</type-mapping> | </metadata> | </local-tx-datasource> | | <mbean code="org.jboss.security.auth.login.DynamicLoginConfig" | name="jboss.security.tests:service=SecuritySpecLoginConfig"> | <attribute name="AuthConfig">login-config.xml</attribute> | <depends optional-attribute-name="LoginConfigService"> | jboss.security:service=XMLLoginConfig | </depends> | <depends optional-attribute-name="SecurityManagerService"> | jboss.security:service=JaasSecurityManager | </depends> | </mbean> | Which also contains a further known bug (FAQ), in that the security MBean is deployed after the datasource (they are deployed in file order). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4122258#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...