| Summary: | Implement 2FA for the OPAC | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Magnus Enger <magnus> |
| Component: | Authentication | Assignee: | Bugs List <koha-bugs> |
| Status: | NEW --- | QA Contact: | Testopia <testopia> |
| Severity: | enhancement | ||
| Priority: | P5 - low | CC: | aude.charillon, dpavlin, hdunne-howrie |
| Version: | Main | ||
| Hardware: | All | ||
| OS: | All | ||
| 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: | |||
|
Description
Magnus Enger
2025-09-24 09:07:48 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? 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. |