Bugs item #551128, was opened at 2002-05-01 12:05
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=551128&group_id=22866

Category: CatalinaBundle
Group: None
>Status: Closed
>Resolution: Wont Fix
Priority: 5
Submitted By: Luke Taylor (luke_t)
Assigned to: Scott M Stark (starksm)
Summary: getUserPrincipal returns null

Initial Comment:
With the 2.4.5RC3 Catalina bundle:

If I login (form-based, j_security_check style) in
order to access a protected resource (/restricted/*),
things go OK and I end up authenticated in the current
session - I can call HttpRequest.getUserPrincipal() OK.

However, if I then submit a request to a non-protected
URL (e.g. a test jsp in the context root),
getUserPrincipal() returns null.

I've noticed this in passing before, but haven't
checked it out previously - I suspect it applies to all
the integrated Catalina versions. It doesn't happen
with standalone Catalina or the JBoss/Tomcat_3.2.3 bundle.

----------------------------------------------------------------------

>Comment By: Scott M Stark (starksm)
Date: 2002-05-01 16:09

Message:
Logged In: YES 
user_id=175228

Its not defined by the servlet spec that the principal 
information should propagate across the session 
irrespective of permissions. I asked about this behavior on 
the servlet list and that was their reply. Standalone 
tomcat bahaves differently because it caches principals in 
a way that does not work when integrated with JBoss.

----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=551128&group_id=22866

_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to