TPAC: Doesn't warn to reauthenticate after Staff Login Timeout expires

Bug #1056252 reported by Michael Peters on 2012-09-25
This bug report is a duplicate of:  Bug #1036318: OPAC timeout within the client. Edit Remove
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Evergreen
Undecided
Unassigned

Bug Description

Evergreen 2.2

Other interfaces in the staff client provide a chance for the user to quickly reauthenticate if their session has expired.

TPAC, unfortunately, does not. There is no cue that a timeout has occurred, except for the fact that the user is prompted to "log in" when placing a hold, or other similar action.

Is it possible to provide a chance to get a new auth token before accessing TPAC within the staff client?

Thomas Berezansky (tsbere) wrote :

Adding an authtoken check on new browser windows may be a decent option, but won't help for windows that time out once opened.

Teaching the OPAC Wrapper to check authtime and re-prompt as needed might work....but I think that is just the timeout, so we probably need to keep track of when we last talked to the server due to automatic extension of authtoken valid periods.

Changed in evergreen:
status: New → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers