Bug 25823 - Add touch authentication capability to opac
Summary: Add touch authentication capability to opac
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: OPAC (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-06-19 15:49 UTC by Christopher Brannon
Modified: 2020-06-20 19:35 UTC (History)
0 users

See Also:
Change sponsored?: ---
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 Christopher Brannon 2020-06-19 15:49:18 UTC
Is there a way to incorporate touch authentication to the opac on mobile devices?
Comment 1 Owen Leonard 2020-06-19 16:19:36 UTC
Have you seen other web sites implement touch authentication?
Comment 2 Christopher Brannon 2020-06-19 17:24:19 UTC
(In reply to Owen Leonard from comment #1)
> Have you seen other web sites implement touch authentication?

Hmmmm.....come to think of it, perhaps not.  I get confused easily between apps and websites.  :/  But, why not try to figure something cutting edge out.  It is a feature being discused, but don't know if it is possible yet.
Comment 3 Katrin Fischer 2020-06-20 16:13:34 UTC
Can you explain how touch authentication works? I am not familiar with it.
Comment 4 Christopher Brannon 2020-06-20 16:49:49 UTC
(In reply to Katrin Fischer from comment #3)
> Can you explain how touch authentication works? I am not familiar with it.

Generally, in an app, like on a phone, you can enable touch authentication, which authorizes a stored touch ID on device, such as a phone, to verify your identity on phones or pads that have fingerprint readers.  You can link sites to this stored authorization.  If your device can verify your identity, it tells the site you are the person that is linked to this ID, and the site logs you in.  I've seen this authorization primarily with apps, but it is probable that this can be extended to websites.  I don't know if it is implemented on websites yet, but I am seeing discussion on the topic.