https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41270
Bug ID: 41270
Summary: Two-factor authentication does not create entry in
action_logs
Initiative type: ---
Sponsorship ---
status:
Product: Koha
Version: 24.11
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5 - low
Component: Transaction logs
Assignee: [email protected]
Reporter: [email protected]
QA Contact: [email protected]
In advance of updating our production server from 22.11 LTS to 24.11 LTS, we
are testing the use of the system preferences TwoFactorAuthentication (Enable)
and TrackLastPatronActivityTriggers (Logging in) on the test server that has
undergone this upgrade.
I have enabled two-factor authentication on my own account.
While examining the relationship between borrowers.lastseen and
action_logs.timestamp, I noticed that the value for my lastseen in borrowers
could not be correlated to an entry in action_logs. The last SUCCESS action for
the AUTH module in action_logs appears to correlate only with the submission of
the correct username and password. The timestamp for lastseen is newer and
seems to correlate with the submission of the correct OTP code.
There ought to be an entry in action_logs that reflects the success or failure
of the 2FA challenge.
Thanks!
--
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.
_______________________________________________
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/