Bug 7499 - CAS authentication breaks saving system preferences
Summary: CAS authentication breaks saving system preferences
Status: CLOSED FIXED
Alias: None
Product: Koha
Classification: Unclassified
Component: Authentication (show other bugs)
Version: Main
Hardware: All All
: P3 critical (vote)
Assignee: Galen Charlton
QA Contact: Ian Walls
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-03 18:56 UTC by Tom Hanstra
Modified: 2019-06-27 09:24 UTC (History)
5 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tom Hanstra 2012-02-03 18:56:59 UTC
When attempting to assign the anonymous patron in the OPAC settings, I receive an error that I'm not logged in even though I am. 

I did not see anything in the logs which give a reason for this.
Comment 1 Tom Hanstra 2012-02-28 20:41:35 UTC
I'm expanding and updating this bug.  It is not only that I cannot set the anonymous patron.  That was just the first thing I found I could not set.  Instead, what I have found is that I cannot change *any* system preference values if I have CAS logins turned on.  

We rely on CAS logins for our OPAC login options.  We don't want CAS to interfere with our STAFF side logins, however.  But with CAS turned on, we receive an error that changes cannot be saved because of we are not logged in.  The error in the message log:

Message Log

    Error; your data might not have been saved
    You need to log in again, your session has timed out

This happens whenever we are logged into the Staff client, whether we are logged into CAS or not.  The staff client is improperly checking for logins.

Let me know if I can provide additional details.

Tom
Comment 2 Chris Cormack 2012-02-28 20:43:27 UTC
Ohhh good catch Tom.

Ill actually bump this to critical. I can replicate also
Comment 3 Julian Maurice 2012-02-29 08:16:04 UTC
Isn't this already fixed by Bug 6694 (Pushed to master) ?
Comment 4 Katrin Fischer 2012-03-19 06:22:04 UTC
Hi Tom, 
I tested this with casAuthentication set to 'Use'. I logged out, logged in, changed system preferences. It seems fixed to me, so I am closing the bug. Please reopen if you are still experiencing problems!