The following comment has been added to this issue:
Author: Ate Douma
Created: Thu, 14 Oct 2004 8:11 AM
Body:
The Tomcat 5 issue 29406 has been fixed since 2004-07-28 which means that from Tomcat
5.0.28 we can resolve this problem without patching Tomcat ourselves.
Since yesterday, Scott removed the unneeded jmx dependencies from J2, with my vote :-)
But, I overlooked we needed it to be able to compile the patched JAASRealm. Because of
that, Tomcat 5 deployment is currently broken!
Now, if we would bump up the minimal supported version of Tomcat 5 to 5.0.28, we can
drop the need of the patch and at the same time fix the build again.
If nobody objects, I will set the additional (still undocumented!) attribute
useContextClassLoader to false for the JAASRealm in Jetspeed.xml when deploying on
Tomcat 5 and remove the JAASRealm patch.
And of course, the getting-started.html page as well as the Wiki information
concerning the required Tomcat 5 version and the resolved JAASRealm problem shall be
updated by me.
Finally, this issue can then be closed also.
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/JS2-55?page=comments#action_54045
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/JS2-55
Here is an overview of the issue:
---------------------------------------------------------------------
Key: JS2-55
Summary: JAAS Authentication on Tomcat 5
Type: New Feature
Status: Unassigned
Priority: Major
Project: Jetspeed 2
Components:
Security
Versions:
2.0-a1
Assignee:
Reporter: Ate Douma
Created: Tue, 25 May 2004 3:26 PM
Updated: Thu, 14 Oct 2004 8:11 AM
Environment: Tomcat 5.0.24, J2SE 1.4.2_03
Description:
As discussed on the Jetspeed developers mailinglist (thread starts with:
http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgNo=14605) the new behaviour of
Tomcat 5 to set the ContextClassLoader in the JAASRealm to the server classloader
prevents defining LoginModules within the context of an web app.
As a quick solution to this problem the Tomcat 5 JAASRealm is going to be patched to
revert back to the old Tomcat 4 handling.
The preferred solution is that the Tomcat Team would do this themselves or provide it
as an option. Someone should start discussing this with them....
I'll provide a patch implementing the quick fix which will depend on the user property
catalina.version.major=5 to be enforced upon the catalina server: when this condition
is true a patched version of the Tomcat 5.0.24 JAASRealm.java revision 1.6 will be
compiled into the $Tomcat/server/classes directory.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
