https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37060
--- Comment #43 from Jan Kissig <[email protected]> --- (In reply to David Cook from comment #42) > (In reply to Matthias Meusburger from comment #39) > > Hi, > > > > I ran into the same wrong_csrf_token issue, which was fixed by closing and > > re-opening the browser. > > > > I have a feeling that this is linked to Bug 38327, but this has to be > > investigated. > > It would depend on how long you hold on to the session cookie and CSRF token > I suppose. Are you doing authenticating for each interaction KOCT has with > Koha or only sometimes? Every time before committing the circulation data to Koha, KOCT sends a GET /cgi-bin/koha/svc/authentication and retrieves SESSIONID and CSRF-Token from that response. If the response is like <status>ok the circulation data is POSTed to /cgi-bin/koha/offline_circ/service.pl. If the response is like <status>expired a POST /cgi-bin/koha/svc/authentication is made. So KOCT checks the auth status every time before sendign data to Koha but will re-auth when a session is expired. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
