DO NOT REPLY [Bug 36057] New: - The method 'getUserPrincipal()' in class 'org.apache.catalina.connector.Request' returns a not null value after the session has been invalidated and/or recreated

2005-08-06 Thread bugzilla
gzilla/show_bug.cgi?id=36057 Summary: The method 'getUserPrincipal()' in class 'org.apache.catalina.connector.Request' returns a not null value after the session has been invalidated and/or recreated

DO NOT REPLY [Bug 36057] - The method 'getUserPrincipal()' in class 'org.apache.catalina.connector.Request' returns a not null value after the session has been invalidated and/or recreated

2005-08-06 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

getUserPrincipal

2002-12-03 Thread RAamer
Hi all, Why are getUserPrincipal and getRemoteUser returnnig null? I know that they are supposed to return null if the user is not authenticated. What does that mean exactly? I have Tomcat running locally on my machine. What does 'authentication' mean in my context? Thanks R

Question about getUserPrincipal...

2001-07-05 Thread The Anenome
Hi, I posted this question first on tomcat-users, but with no responses. I'm hoping one of you guys will be able to answer this question. I have been using Tomcat 3.1 in the past, and have been using the getUserPrincipal().getName() method to determine who has logged in. I was using a

[Proposal] Fix for getUserPrincipal problem.

2000-12-31 Thread Thom Park
Hello! I have, what I believe is a fix for a problem reported by me earlier with getUserPrincipal, where two separate browser sessions return the same principal, even when the authorized users are different. The proposal is this: In several places in the code there are comments that state that

fix for bug 558, getUserPrincipal returns wrong user

2000-12-08 Thread Brian Moore
I just entered bug 558, but the bug tool ignored the text in the "how to reproduce" and "workaround" fields, which included my suggested bug fix: How to reproduce: Access the jsp/security/protected/index.jsp example then access it again as a different user. getRemoteUser