We have multiple server SSO session authentication set up on our servers. We have a number of users that are getting session timeout messages well before their session should be timing out, seemingly at random lengths of time. When they click OK, they aren’t prompted to log in, though the login window seems to pop up and quickly close. Any thoughts?
Subject: suggestions
I have not heard about this problem before, but will give you some general advice.
First you should check that the SSO server machines are sharing the same notion of what time it is. The machines can be in different time zones, but if the time on each machine were normalized to Greenwich mean time, the machines should be in agreement about the current time, or within a small tolerance. Clock skew is one of the major reasons why you might see unexpected expiration messages.
Second, the Domino web server might be thrashing with too high a volume of users. Web server caches may be configured with values that are too small to handle the volume. For example, you can consider whether to increase the “Maximum cached users” value in the Internet Protocols - Domino Web Engine tab of the server’s Server document in the Domino Directory.
If neither of the above suggestions apply to your environment, I suggest you turn on debugging and look for the errors reported to the server console. For example, in the server notes.ini, you can set an environment variable to send logging information to a file, and set up for SSO tracing:
debug_outfile=c:\tmp\notes.log
DEBUG_SSO_TRACE_LEVEL = 2
hope this helps!
Jane Marcus
Subject: sso expires
you can also issue the console command tell http show users
to see when domino expects the session to expire
it may be an issue with your idles session timeout, see if throttling that back provides your users with relief
Subject: We have the same Problem…
At a random lengths of time our sessions times out. Our users gets error message or a white screen. The login window pop up and quickly close.
The only workaround for now seams to be;
Logout > empty IE cache > Start new browser > New session.
Our enviroment:
-
Windows 2003 servers.
-
8.5 std templates upgraded from 8.01 (iNotes)
-
IE7
Did you found any solution and/or workaround for this annoying behavior?
I created a Service Request (70453 180 846 ) September 15, but still no solution.
Please contace me here or via e-mail [dan.eriksson@orebro.se] if you have more information/help regarding this matter.