Bug 35617 - Make phone number as match point in in Identity providers
Summary: Make phone number as match point in in Identity providers
Status: Needs Signoff
Alias: None
Product: Koha
Classification: Unclassified
Component: Authentication (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Slava Shishkin
QA Contact: Testopia
URL:
Keywords:
Depends on: 31378
Blocks:
  Show dependency treegraph
 
Reported: 2023-12-20 14:34 UTC by Slava Shishkin
Modified: 2023-12-20 15:04 UTC (History)
2 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments
Bug 35617: Extending the matchpoint in "identity_providers" by phone number (4.66 KB, patch)
2023-12-20 15:02 UTC, Slava Shishkin
Details | Diff | Splinter Review

Note You need to log in before you can comment on or make changes to this bug.
Description Slava Shishkin 2023-12-20 14:34:56 UTC
Currently, the system supports match points by -email, -userid, and -cardnumber. Many external authorization systems have the authentication by phone number, which is also required for libraries.
Comment 1 Slava Shishkin 2023-12-20 15:02:44 UTC
Created attachment 160122 [details] [review]
Bug 35617: Extending the matchpoint in "identity_providers"            by phone number

Update identity_providers to include 'phone' as a matchpoint, 
also as option in the dropdown menu. Further when authentication 
phase 'phone' will be used as the matchpoint like email, userid, 
or cardnumber.
Comment 2 Slava Shishkin 2023-12-20 15:04:37 UTC
The new match point for -phone numbers will function exactly as the -email match point as it is implemented now in master with known imperfection: It is known that Koha does not check for email uniqueness for now even if it's a matchpoint, so same behavior present with a phone number field. Making Koha check for uniqueness for any of both fields is much more complicated architecture-wise and should be solved later as a separate task, but this does not limit current use for libraries that already have email or phone as matchpoints anyway.