Bug 41209 - Add the ability to choose an authentication method for patron or patron category
Summary: Add the ability to choose an authentication method for patron or patron category
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Authentication (show other bugs)
Version: 25.05
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-11-06 19:41 UTC by Koha collecto
Modified: 2025-11-06 19:41 UTC (History)
1 user (show)

See Also:
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:


Attachments
How Moodle allows admin to choose an authentication method (25.92 KB, image/png)
2025-11-06 19:41 UTC, Koha collecto
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Koha collecto 2025-11-06 19:41:48 UTC
Created attachment 189218 [details]
How Moodle allows admin to choose an authentication method

Right now when opacuserlogin is activated, all methods of authentication are available for patrons on the OPAC.

So if a library decides to change authentication method (from manual to SSO, for example), they need to either hide the manual login boxes with Javascript or make sure to change the password previewsly used for the manual authentication. Otherwise, the patrons would be able to login with either one of the methods.

It would be great if we could force an authentification method at least in each of the patron categories or even at the patron level. By choosing a an authentication method for a patron or category, that method would be the only one available on the OPAC for that patron or category.

This would :
- be less of a headeache for libraries that decide to change the authentification method.
- be less confusing for patrons that want to login on Koha by only seeing what is available for them
- be more secure than login bozes being hidden by javascript code (not an IT analyst here but i've been told this il a less secure way to manage it).

See the attachment for the propose form (the screencapture was taken from Moodle)