JaasSecurityManagerService JNDI bindings
When you specify a JNDI name, there has to be an object-binding there to use. To simplify the setup of the JNDI name to security manager bindings, the JaasSecurityManagerService manages the association of security manager instances to names by binding a next naming system reference with itself as the JNDI ObjectFactory under the name java:/jaas. This permits a naming convention of the form java:/jaas/XYZ as the value for the element, and the security manager instance for the XYZ security domain will be created as needed. The security manager for the domain XYZ is created on the first lookup against the java:/jaas/XYZ binding by creating an instance of the class specified by the SecurityManagerClassName attribute using a constructor that takes the name of the security domain. Important: java:/jaas prefix is no longer mandatory In Enterprise Application Platform versions prior to v5.0, the "java:/jaas prefix in each deployment descriptor element was required to correctly bind the JNDI name of a security domain to the security manager bindings. As of JBoss Enterprise Application Platform 5, the java:/jaas prefix is not required for security domain declaration. The java:/jaas prefix is still supported, and remains for backward compatibility.