I am trying to deploy a ear file in JB3.0 that previously works correctly in 2.4.6-Tomcat. I believe I have everything is correctly configured, however, when it gets to the point of actually deploying the beans, I am presented with this output to the console:
17:08:31,084 INFO [EjbModule] Deploying References
17:08:31,114 INFO [EjbModule] Deploying ReferenceStatus
17:08:31,144 INFO [EjbModule] Deploying ServiceArea
17:08:31,164 INFO [EjbModule] Deploying Location
17:08:31,185 INFO [EjbModule] Deploying LocationStatus
17:08:31,205 INFO [EjbModule] Deploying ReferenceManager
17:08:31,235 INFO [EjbModule] Deploying UserManager
17:08:31,255 INFO [EjbModule] Deploying GroupManager
at this point, it the login() of DatabaseServerLoginModule is invoked like 40 times, of course failing each time because it says the principal = null.
This is the start of the error that I eventually get:
17:15:45,800 ERROR [EjbModule] Initialization failed
java.lang.SecurityException: Invalid authentication attempt, principal=null
My first question is: How can I fix this problem.
My second question is: Why, at this point of the deploy, would JBoss need to login()?
Your help is greatly appreciated, please let me know if you need any more information.
I get a similar result. I did two things:
1.) setup a DatabaseServerLoginModule in my login-config.xml file.
2.)set the security domain JNDi name in my mssql-service.xml file to point to this security domain
And now I cannot deploy my .ear! Anyone know what is causing JBoss to login() with a null principal during deployment?