[
http://jira.jboss.com/jira/browse/JBCLUSTER-148?page=comments#action_1234... ]
Alberto Rodriguez commented on JBCLUSTER-148:
---------------------------------------------
It's been pointed in Tomcat's developers list that section 7.7.2 (Distributed
Environments) of JSR-154 (Servlet specfication) is said:
"Within an application marked as distributable, all requests that are part of a
session must be handled by one Java Virtual Machine at a time"
This invalidates our approach unless that paragraph is changed in subsecuent revisions of
the specfication ( this probably won't happen in the near future because of it's
distributed VM shynchronization implications).
Include Tomcat's SavedRequest object into the replication process
in a Jboss-Tomcat clustered environment to allow proper Single Sign On capabilities
-----------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBCLUSTER-148
URL:
http://jira.jboss.com/jira/browse/JBCLUSTER-148
Project: JBoss Clustering
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: Q2Y6
Environment: independent
Reporter: Alberto Rodriguez
Assigned To: Brian Stansberry
Priority: Optional
Original Estimate: 6 weeks
Remaining Estimate: 6 weeks
In a JBoss clustered environment where session is replicated and single sign on is
enabled, one cannot log in an protected clustered web application because of the lack of
Serialization support of Tomcat's SavedRequest object.
Tomcat stores the information needed to restore the pre-authentication request in a note
in the session in a SavedRequest object, this object is not included in the replication
process because it doesn't implement Serializable.
The objective would be to make SavedRequest object Serializable in Tomcat and include
this object and/or other notes in the serialization process executed when the session info
is replicated.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira