| Summary: | Patron verification through SMS one time code | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Christopher Brannon <cbrannon> |
| Component: | Patrons | Assignee: | Bugs List <koha-bugs> |
| Status: | NEW --- | QA Contact: | Testopia <testopia> |
| Severity: | enhancement | ||
| Priority: | P5 - low | CC: | dcook, gmcharlt, kyle, magnus |
| 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
Christopher Brannon
2020-08-06 19:19:40 UTC
I don't know about that first use case, although I suppose it's not that different to authenticating someone by scanning a card (ie something they *have* rather than something they *know*). That could be an interesting Koha Plugin. I like the second use case better. Using it to validate setting up SMS messaging, or being used as a 2nd factor for authentication (ie something they *have* PLUS something the password that they *know*). I could also see this method via email as well, in verifying the patron, and in verifying an email address (outside of the initial self registration method). |