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=28039>. 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=28039 Cluster Support for SingleSignOn Summary: Cluster Support for SingleSignOn Product: Tomcat 5 Version: Nightly Build Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The attached patch is a first step aimed at enabling TC's SingleSignOn function to work across a cluster. It includes the following: 1) Interface SSOClusterManager, which should be implemented by a class that provides SSO support across a cluster. 2) Changes to SingleSignOn (and related classes) to add an MBean attribute for specifying an implementation of SSOClusterManager to use. If an SSOClusterManager is set, invokes it when changes are made to the SSO entries on the local cluster node or if the cluster needs to be queried for a non- local SSO. 3) An abstract base implementation of SSOClusterManager that concrete subclasses can build upon. FYI, I have also attached a concrete implementation, a JBossSSOClusterManager. It uses the JBoss TreeCache to communicate SSO changes across the cluster. I've tested this in the JBoss/Tomcat integration. I know you can't use TreeCache in TC because of license issues, but thought you might be interested in a concrete implementation. Sorry, I haven't had a chance to look into how Tomcat's own cluster communication works. If you're interested in this patch I can look into what it would take to implement a TC-only version. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]