Could someone explain how to set the session timeouts such that the staff stay logged in for the day without timing out but the OPAC times out after 15 minutes? Lori =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-= Lori Bowen Ayre // Library Technology Consultant The Galecia Group // www.galecia.com (707) 763-6869 // Lori.Ayre@galecia.com <Lori.Ayre@galecia.com>Specializing in open source ILS solutions, RFID, filtering, and automated materials handling (AMH) =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2010/11/24 Lori Bowen Ayre <lori.ayre@galecia.com>
Could someone explain how to set the session timeouts such that the staff stay logged in for the day without timing out but the OPAC times out after 15 minutes?
To my knowledge there is only one timeout setting used for both OPAC and the staff client: timeout This is set in seconds. I do agree that it would be nice to have two separate session timeout settings. Kind Regards, Chris
I read somewhere about using different domains to specify the staff time out setting versus the public time out settings...some cookie trickery? Lori On Wed, Nov 24, 2010 at 7:00 PM, Chris Nighswonger < cnighswonger@foundations.edu> wrote:
2010/11/24 Lori Bowen Ayre <lori.ayre@galecia.com>
Could someone explain how to set the session timeouts such that the staff
stay logged in for the day without timing out but the OPAC times out after 15 minutes?
To my knowledge there is only one timeout setting used for both OPAC and the staff client: timeout
This is set in seconds.
I do agree that it would be nice to have two separate session timeout settings.
Kind Regards, Chris
-- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-= Lori Bowen Ayre // Library Technology Consultant The Galecia Group // www.galecia.com (707) 763-6869 // Lori.Ayre@galecia.com <Lori.Ayre@galecia.com>Specializing in open source ILS solutions, RFID, filtering, and automated materials handling (AMH) =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
The idea behind the shorter staff time out is that the staff should be able to login in the morning and stay logged in all day. The public on the other hand may login to their accounts and look up some items in the catalog and mayb renew some items and then go home. If they fail to logout, their account is compromised. Doesn't that justify setting a significantly shortly time out for the them? Lori On Thu, Nov 25, 2010 at 12:01 AM, Stefano Bargioni <bargioni@pusc.it> wrote:
On Nov 25, 2010, at 04:00 , Chris Nighswonger wrote:
I do agree that it would be nice to have two separate session timeout settings.
This is my opinion too. More, in my opinion the staff timeout is unnecessary. sb _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-= Lori Bowen Ayre // Library Technology Consultant The Galecia Group // www.galecia.com (707) 763-6869 // Lori.Ayre@galecia.com <Lori.Ayre@galecia.com>Specializing in open source ILS solutions, RFID, filtering, and automated materials handling (AMH) =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
participants (3)
-
Chris Nighswonger -
Lori Bowen Ayre -
Stefano Bargioni