| Summary: | 2FA - Trust current device | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Sam S <tech.sam> |
| Component: | Staff interface | Assignee: | Bugs List <koha-bugs> |
| Status: | NEW --- | QA Contact: | Testopia <testopia> |
| Severity: | enhancement | ||
| Priority: | P5 - low | CC: | andrew.auld, chris.rowlands6, dcook, gmcharlt, helm.consortium, pedro.amorim |
| 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: | |||
| Bug Depends on: | 20476 | ||
| Bug Blocks: | |||
|
Description
Sam S
2023-03-16 16:55:43 UTC
This is definitely a quality of life feature that our libraries would appreciate. We have had this feedback a few times since MFA implementation has become a requirement in UK public sector systems. I reckon this would be easy enough to add. This is a good example of where a "borrowers_credentials" table would be great, as we could store a "mfa_token". And then the user could have a cookie with that token. |