|
The time-out that you are looking for the is Idle session time-out, as you mentioned below. However, this setting is impacted by your sso (single sign on) setting. If you have SSO set to "Single Server", then the value is related back to user inactivity. If you have SSO set to multi-server, it is an absolute ticket expiration. I.E. 30 minutes would mean that the user will be logged off in 30 minutes, regardless of activity. This is because in multi-server mode, the server hands out an LTPA token (i.e. cookie) that has an expiration date. You can hit another other server in the same domain that is part of the SSO config without re-authenticating (read Websphere), but you lose the ability to update that token. The other values that you mentioned are centered around server process terminating i.e. if a CGI program runs for a too long, it will be timed-out. Session state tracking: Enabled Idle session time-out: 30 minutes David Hoff 3X Corporation Phone: 678-579-0170 x205 email: david.hoff@xxxxxx web: www.3x.com domino400-request@xxxxxxxxxxxx Sent by: domino400-bounces@xxxxxxxxxxxx 03/31/2003 01:00 PM Please respond to domino400@xxxxxxxxxxxx To domino400@xxxxxxxxxxxx cc Subject Domino400 Digest, Vol 1, Issue 303 Send Domino400 mailing list submissions to domino400@xxxxxxxxxxxx To subscribe or unsubscribe via the World Wide Web, visit http://lists.midrange.com/mailman/listinfo/domino400 or, via email, send a message with subject or body 'help' to domino400-request@xxxxxxxxxxxx You can reach the person managing the list at domino400-owner@xxxxxxxxxxxx When replying, please edit your Subject line so it is more specific than "Re: Contents of Domino400 digest..." Today's Topics: 1. Time-outs (Mike.Crump@xxxxxxxxxxxxxxxx) ---------------------------------------------------------------------- message: 1 date: Mon, 31 Mar 2003 09:06:20 -0500 from: Mike.Crump@xxxxxxxxxxxxxxxx subject: Time-outs I'm working with a Domino 5.08 server and have a question with session time-outs with a browser application that we have. I have a handful of users complaining about getting knocked out of the application and being forced to sign-on again. I would understand that activity within the browser doesn't equate back to the server. But in checking the server settings I see a number of time-out values and I'm not sure if I grasp what they all could be. On the HTTP Internet Protocols Tab I see the following settings: Input time-out: 2 minutes Output time-out: 20 minutes CGI time-out: 5 minutes Idle thread time-out: 0 minutes On the Domino Web Engine Internet Protocols Tab for Java Servlet I have this: Session state tracking: Enabled Idle session time-out: 30 minutes So, is this all of time out values available? Effectively, what I am after is an environment where inactivity is handled as similar as it is an the AS/400 QINACTITV. I may not be thinking properly from a Domino/HTTP perspective but if a user is inactive after a period of time then I need to have them disconnected and I want to do it consistently. For example, can one assume that the Java Servlet time-out and Output time-out be considered somewhat similar? Michael Crump Saint-Gobain Containers 1509 S. Macedonia Ave. Muncie, IN 47302 (765)741-7696 (765)741-7012 f (800)428-8642 "We will meet that threat now with our Army, Air Force, Navy, Coast Guard, and Marines so that we do not have to meet it later with armies of firefighters and police and doctors on the streets of our cities." George W. Bush March 19, 2003 www.standwithbush.com ------------------------------ _______________________________________________ This is the Lotus Domino on the iSeries / AS400 (Domino400) digest list To post a message email: Domino400@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/domino400 or email: Domino400-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/domino400. End of Domino400 Digest, Vol 1, Issue 303 *****************************************
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.