On 30 Jan 2008, at 17:57, Wesley Craig wrote: > On 29 Jan 2008, at 17:06, Simon Wilkinson wrote: >> What should probably happen is that when cosign can't find a >> ticket cache on the first server, it tries the second one - this >> doesn't seem to currently happen. > > We have an open bug report for this behavior on the Java filter. > No similar report for IIS or apache cosign filter, tho.
We definitely see this occasionaly. It may be related to some other strange behaviour we're seeing, though. It looks like the Apache cosign filter sometimes drops cosign servers from its list of hosts to try, so you end up with the filter only knowing about one of the servers. If that server happens to have not received the replicated cookie details, the end user can see infinite loops between the service and the weblogin site. It looks like the server list that check_cookie uses is using is getting truncated somewhere along the way, but so far, beyond confirming that when the problem occurs there is only one server in that list (we normally have two), I haven't really got anywhere. Any thoughts? Cheers, Simon. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Cosign-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cosign-discuss
