Bug 40867 - Implement 2FA for the OPAC
Summary: Implement 2FA for the OPAC
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Authentication (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-09-24 09:07 UTC by Magnus Enger
Modified: 2026-02-04 17:14 UTC (History)
3 users (show)

See Also:
GIT URL:
Initiative type: ---
Sponsorship status: ---
Comma delimited list of Sponsors:
Crowdfunding goal: 0
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Magnus Enger 2025-09-24 09:07:48 UTC
We have 2FA for the staff interface, it would be nice to have it for the OPAC too. It should probably be a separate options, so 2FA can be enabled/enforced separately for the staff interface and for the OPAC.
Comment 1 Hannah Dunne-Howrie 2026-02-04 17:01:44 UTC
We seconded this suggestion. Our library users are increasingly concerned about cyber security. The only thing I'd want to add though is how would this work with the patron API and SIP2?
Comment 2 Aude Charillon 2026-02-04 17:14:31 UTC
Other library catalogues and discovery platforms offer two-factor authentication for library members (e.g. Aspen Discovery https://aspen-discovery.atlassian.net/wiki/spaces/Help/pages/339443716/Logging+In#Two-Factor-Authentication) It could be useful to compare this with how we would want things to work in Koha.