DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=33713>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=33713 Summary: Admin webapp throws NullPointerException when logon is performed using Single Sign On Product: Tomcat 5 Version: 5.5.7 Platform: PC OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component: Webapps:Administration AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] If Single Sign On is enabled, a user can visit the Tomcat administration webapp after logging on using another page. Unfortunately after upgrading from Tomcat 5.0 to 5.5.7 we've found this results in a NullPointerException (unless the admin webapp has already been loaded). I've had a look at the code, and the reason seems to be Remm's commit to web.xml and login.jsp on 16-Aug-04 (affecting Tomcat 5.5.0 and above) that stopped the admin app being loaded on startup and instead loads its internals when the login .jsp page is visited. This fix obviously assumes that the login page is always visited before the admin webapp is accessed - an assumption that is not valid when using SSO. I suggest either reversing the previous commit and turning load-on-startup on again; or alternatively, adding the line that was added to login.jsp to frameset.jsp as well (someone would need to confirm if this works OK, as I don't know). -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
