Servlet init() calling secured EJBs

[sgodden]

I have an app which requires that on system startup, various initialisation is performed, which results a) in system delivered data being created, and b) some utility objects being bound into JNDI.

I am doing this work in the init() method of a servlet which is deployed within my EAR.

Unfortunately, if I secure my EJBs, then the servlet cannot access them, as it runs under a null user principal. Run-as role doesn't help that.

I tried doing an explicit client login to the domain in question within the init() method. The login succeeds, but I still get the same null principal errors when it tries to access the secured EJBs.

Can anyone suggest how I should perform this initialisation in a secured environment? I need to be portable, which is why I have used a servlet init() method up to now.

[ahardy66]

"sgodden" wrote:

Unfortunately, if I secure my EJBs, then the servlet cannot access them, as it runs under a null user principal. Run-as role doesn't help that.

Are you sure? From reading the servlet spec just now, run-as seems to be exactly what you need. Do you have the role specified properly in the web.xml? Are you sure your principal is null in the EJB? And are you sure you have specified that that role can use that EJB?

[starksm64]

There is an open bug report that will be fixed for 4.0.3:

http://jira.jboss.com/jira/browse/JBAS-2015