Hi, guys

I am running into problems with Jetty + JBoss 3.0alpha

After some debugging here is what I have. 

Setup:
Jetty + JBoss 3.0
Sun's Petstore 1.1.1 deployed piecewise (meaning each EJB and WAR are
packaged separately and deployed in a J2eeScopedDeployer)
JBossSX configured to pick up usernames, password and roles from files

Here is what happens: 

1) a servlet in Petstore takes username and password from a Web form and
sets "j_username" and "j_password" in the session. Jetty seems to pick
this stuff up and pass it to JBossUserRealm to authenticate the user.
JbossUserPrincipal gets created and then proceeds to authenticate with
with _securityMgr (which is JaasSecurityManager "java:/jaas/other").
Authentication succeeds, I see a log and I did doublecheck that
JaasSecurityManager sets activeSubject to this authenticated subject.

2) Then, it seems, Jetty proceeds to check that this user has required
roles. It first calls JbossUserRealm.getUser(name) to obtain the
JBossUserPricipal and then calls isUserInRole(String role). This is where
the stuff fails miserably. The reason being that Jetty dispatched a
different thread to do role checking than the one that did
authentication. Because of this, JaasSecurityManager sees a null
activeSubject and says that the user does not have required roles.

Now, this happens in a _single_ http request from a web client (just
clicked 'login' button on a form). I can try hacking a workaround just for
my demo to work but would like to help fixing this if it is a bug. 

-------------------------------------------------------------------------
Anatoly Akkerman
Computer Science Dept.
Courant Institute of Mathematical Sciences, NYU
715 Broadway, #719                      Tel: 212 998-3493
New York, NY 10003                      Fax: 212 995-4123
-------------------------------------------------------------------------


_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to