Can someone clarify the timeout system preference? In the 3.0.x manual site, it says Inactivity timeout for cookies authentication (in seconds). This preference applies to both the staff client and the OPAC. Default Value: 12000000 If I'm doing the math right, the default value translates to an extremely large number of hours. Is seconds right for this value? Or should it be milliseconds? If seconds is correct, can someone give me background on why the default is so large, and why the manual says it shouldn't be changed after installation? I don't want to make changes here until I'm sure of what it's doing. Thanks much! Jane Wagner Library Systems Analyst PTFS Inc. Content Management and Library Solutions 6400 Goldsboro Road, Suite 200 Bethesda, MD 20817 (301) 654-8088 x 151 jwagner@ptfs.com
Wagner, Jane a écrit :
Can someone clarify the timeout system preference? In the 3.0.x manual site, it says
Hi Jane,
Inactivity timeout for cookies authentication (in seconds). This preference applies to both the staff client and the OPAC.
Default Value: 12000000
If I'm doing the math right, the default value translates to an extremely large number of hours. Is seconds right for this value? Or should it be milliseconds?
nope, it's seconds.
If seconds is correct, can someone give me background on why the default is so large, and why the manual says it shouldn't be changed after installation? I don't want to make changes here until I'm sure of what it's doing.
I really don't know. On french, doc, this is not specified, and nothing justify this. Just don't put 1 or 2, as in 1 second, you'll be disconnected very quickly ;-) -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08
On Tue, Feb 24, 2009 at 7:15 PM, paul POULAIN <paul.poulain@biblibre.com> wrote:
Wagner, Jane a écrit :
Can someone clarify the timeout system preference? In the 3.0.x manual site, it says
Hi Jane,
Inactivity timeout for cookies authentication (in seconds). This preference applies to both the staff client and the OPAC.
Default Value: 12000000
If I'm doing the math right, the default value translates to an extremely large number of hours. Is seconds right for this value? Or should it be milliseconds?
nope, it's seconds.
If seconds is correct, can someone give me background on why the default is so large, and why the manual says it shouldn't be changed after installation? I don't want to make changes here until I'm sure of what it's doing.
I really don't know. On french, doc, this is not specified, and nothing justify this. Just don't put 1 or 2, as in 1 second, you'll be disconnected very quickly ;-)
I think at some point someone probably complained they were getting disconnected too much so it got set to a really high value. Chris
On Tue, Feb 24, 2009 at 7:33 AM, Chris Cormack <chris@bigballofwax.co.nz> wrote:
On Tue, Feb 24, 2009 at 7:15 PM, paul POULAIN <paul.poulain@biblibre.com> wrote:
Wagner, Jane a écrit :
Can someone clarify the timeout system preference? In the 3.0.x manual site, it says
Hi Jane,
Inactivity timeout for cookies authentication (in seconds). This preference applies to both the staff client and the OPAC.
Default Value: 12000000
I think at some point someone probably complained they were getting disconnected too much so it got set to a really high value.
One problem is : as far as I can see, there's only one timeout, while there probably should be 2 : one for opac, one for intranet. Short for opac, long for intranet, where you want to : start cataloging a book, go have a coffee, continue cataloging that darn book. my 2 cts Nicolas
Chris _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
-- Nicolas Morin Mobile: +33(0)633 19 11 36 http://www.biblibre.com
-----Original Message----- On Tue, Feb 24, 2009 at 7:33 AM, Chris Cormack <chris@bigballofwax.co.nz> wrote:
On Tue, Feb 24, 2009 at 7:15 PM, paul POULAIN <paul.poulain@biblibre.com> wrote:
Wagner, Jane a écrit :
Can someone clarify the timeout system preference? In the 3.0.x manual site, it says
Hi Jane,
Inactivity timeout for cookies authentication (in seconds). This preference applies to both the staff client and the OPAC.
Default Value: 12000000
I think at some point someone probably complained they were getting disconnected too much so it got set to a really high value.
One problem is : as far as I can see, there's only one timeout, while there probably should be 2 : one for opac, one for intranet. Short for opac, long for intranet, where you want to : start cataloging a book, go have a coffee, continue cataloging that darn book. my 2 cts Nicolas That's one reason I was looking at the syspref (thanks to all for the responses). It would be useful to specify that an OPAC session should close after x minutes of inactivity -- especially for a public workstation in a library. However, a staff session should have a much longer timeout. We may try to do something with this at some point.... Jane Wagner Library Systems Analyst PTFS Inc. Content Management and Library Solutions 6400 Goldsboro Road, Suite 200 Bethesda, MD 20817 (301) 654-8088 x 151 jwagner@ptfs.com
Chris _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
-- Nicolas Morin Mobile: +33(0)633 19 11 36 http://www.biblibre.com _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Wagner, Jane skrev:
-----Original Message----- On Tue, Feb 24, 2009 at 7:33 AM, Chris Cormack <chris@bigballofwax.co.nz> wrote:
On Tue, Feb 24, 2009 at 7:15 PM, paul POULAIN <paul.poulain@biblibre.com> wrote:
Wagner, Jane a écrit :
Can someone clarify the timeout system preference? In the 3.0.x manual site, it says
Hi Jane,
Inactivity timeout for cookies authentication (in seconds). This preference applies to both the staff client and the OPAC.
Default Value: 12000000
I think at some point someone probably complained they were getting disconnected too much so it got set to a really high value.
One problem is : as far as I can see, there's only one timeout, while there probably should be 2 : one for opac, one for intranet. Short for opac, long for intranet, where you want to : start cataloging a book, go have a coffee, continue cataloging that darn book. my 2 cts Nicolas
That's one reason I was looking at the syspref (thanks to all for the responses). It would be useful to specify that an OPAC session should close after x minutes of inactivity -- especially for a public workstation in a library. However, a staff session should have a much longer timeout. We may try to do something with this at some point....
At the same time perhaps also make it possible to log in as another user in opac as in staff on the same computer? I am sometimes confused that I have to log out of staff to test a user in opac, unless I have a separate machine to do this on. Best regards Axel Bojer
One problem is : as far as I can see, there's only one timeout, while there probably should be 2 : one for opac, one for intranet.
Agreed on that point, FWIW.
At the same time perhaps also make it possible to log in as another user in opac as in staff on the same computer?
What version are you using Axel? As far as I know this has been fixed in 3.0. -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org
Owen Leonard skrev:
One problem is : as far as I can see, there's only one timeout, while there probably should be 2 : one for opac, one for intranet.
Agreed on that point, FWIW.
At the same time perhaps also make it possible to log in as another user in opac as in staff on the same computer?
What version are you using Axel? As far as I know this has been fixed in 3.0.
3.0. I will check in on it once more. Best regards Axel Bojer
What version are you using Axel? As far as I know this has been fixed in 3.0.
3.0. I will check in on it once more.
It sounds from Chris's post that it's "fixed" for me because I've always tested under the conditions he describes:
An easy way to do this presently is to setup a different virtualhost name for the staff interface.
-- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org
On Tue, Feb 24, 2009 at 8:44 AM, Axel Bojer <axelb@skolelinux.no> wrote:
Wagner, Jane skrev:
-----Original Message----- On Tue, Feb 24, 2009 at 7:33 AM, Chris Cormack <chris@bigballofwax.co.nz> wrote:
On Tue, Feb 24, 2009 at 7:15 PM, paul POULAIN <paul.poulain@biblibre.com> wrote:
Wagner, Jane a écrit :
Can someone clarify the timeout system preference? In the 3.0.x manual site, it says
Hi Jane,
Inactivity timeout for cookies authentication (in seconds). This preference applies to both the staff client and the OPAC.
Default Value: 12000000
I think at some point someone probably complained they were getting disconnected too much so it got set to a really high value.
One problem is : as far as I can see, there's only one timeout, while there probably should be 2 : one for opac, one for intranet. Short for opac, long for intranet, where you want to : start cataloging a book, go have a coffee, continue cataloging that darn book. my 2 cts Nicolas
That's one reason I was looking at the syspref (thanks to all for the responses). It would be useful to specify that an OPAC session should close after x minutes of inactivity -- especially for a public workstation in a library. However, a staff session should have a much longer timeout. We may try to do something with this at some point....
At the same time perhaps also make it possible to log in as another user in opac as in staff on the same computer? I am sometimes confused that I have to log out of staff to test a user in opac, unless I have a separate machine to do this on.
An easy way to do this presently is to setup a different virtualhost name for the staff interface. IE. opac.foo.bar for OPAC staff.foo.bar for staff Regards, Chris
Chris Nighswonger a écrit :
An easy way to do this presently is to setup a different virtualhost name for the staff interface.
IE.
opac.foo.bar for OPAC
staff.foo.bar for staff
foo.bar and foo.bar:8080 NOT being different vhosts, just different ports. I consider this as a feature ;-) -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08
One problem is : as far as I can see, there's only one timeout, while there probably should be 2 : one for opac, one for intranet. Short for opac, long for intranet, where you want to : start cataloging a book, go have a coffee, continue cataloging that darn book.
What about letting the user decide? This could be a per user setting. The default may be short, but the user can set this value to a larger one if he wanted. I can understand that having a short timeout for a public workstation is probably the best, but this is not very useful for the user accessing the OPAC from home. Eric
On Tue, Feb 24, 2009 at 9:35 AM, Eric Bégin <Eric.Begin@inlibro.com> wrote:
One problem is : as far as I can see, there's only one timeout, while there probably should be 2 : one for opac, one for intranet. Short for opac, long for intranet, where you want to : start cataloging a book, go have a coffee, continue cataloging that darn book. What about letting the user decide? This could be a per user setting.
I don't see any value to that. There are security implications from session length, so the MAX session length should be controlled by the system, not the user. The user can always logout earlier if they want to. On the question of logging into the OPAC as a different user, it is only a problem if you do not have separate DNS names for your interfaces. The session data is written in a cookie, and cookies do not distinguish between interfaces based on ports, only by domain. So it is recommended to use different DNS names instead of samename:8080. --Joe
Personally, I am not going to trust a user's home computer to be any more secure than one of my OPAC workstations. I actually expect a home computer to be less secure, because I might have internet filtering in place to protect my OPAC workstations from the more malicious sites. Or I may have a dedicated IT staff to keep the workstations clean of such problems. A home computer isn't likely to have either. On Tue, 2009-02-24 at 09:35 -0500, Eric Bégin wrote:
One problem is : as far as I can see, there's only one timeout, while there probably should be 2 : one for opac, one for intranet. Short for opac, long for intranet, where you want to : start cataloging a book, go have a coffee, continue cataloging that darn book.
What about letting the user decide? This could be a per user setting. The default may be short, but the user can set this value to a larger one if he wanted.
I can understand that having a short timeout for a public workstation is probably the best, but this is not very useful for the user accessing the OPAC from home.
Eric _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel -- Michael Hafen Systems Analyst and Programmer Washington County School District Utah, USA
for Koha checkout http://koha-dev.washk12.org or git://koha-dev.washk12.org/koha
participants (10)
-
Axel Bojer -
Chris Cormack -
Chris Nighswonger -
Eric Bégin -
Joe Atzberger -
Michael Hafen -
Nicolas Morin -
Owen Leonard -
paul POULAIN -
Wagner, Jane