DynamicLoginConfig problems

[sradford]

Hi,

I have deployed my own ServerLoginModule via the DynamicLoginConfig (in a sar within an ear, called ear1). It is deployed as xxxRealm.

When I connect to EJB's deployed withing ear1, secured by the xxxRealm all works fine.

I now have a second ear, say ear2, which deploys more ejbs, secured by the above xxxRealm.

However, when I try to access the ejbs in in ear2 I get nowhere.

I get the classic [org.jboss.ejb.plugins.SecurityInterceptor] Authentication exception, principal=(null or XXX) deplending on wherever I do the client login or not.

When accessing these ear2 ejbs my ServerLoginModule does not get initialised (no log messages). Any ideas why?

Regards,

Sean

(using Jboss-3.2.6)

[sradford]

I guess I should add that both my ears have different loader-repositories specified via their jboss-app.xml file.

[starksm64]

Presumably the second ear has no visibility to the ServerLoginModule due to the scoping then. Enable trace level logging on the security category org.jboss.security (http://www.jboss.org/wiki/Wiki.jsp?page=Logging) to better see what is failing. The sar setting up the shared security domain clearly should not be within a scoped ear.

[sradford]

I have worked out that the following was happening.

- The xxxRealm was being 'found' from with ear2
- The ServerLoginModule for the xxxRealm was then causing an class not found exception (it dynamically loads classes, and the one it required was only in ear1).
- This exception was then being swallowed and the principal=null exception thrown.

Sean