--- Comment #8 from Alex Arnaud <> ---
(In reply to Kyle M Hall from comment #5)
> (In reply to Alex Arnaud from comment #4)
> > (In reply to Kyle M Hall from comment #3)

> I would say the plugin itself should be responsible for having controls to
> tell Koha if it is enabled or not. There is already precedence for this in
> Koha ( see bug 19173 ). For simplicity, the plugin could simply return
> values as if the authentication failed, for the sake of simplicity.
> What do you think?

You mean: plugin exists (in the plugins directory) == plugin enabled ? That
also means we need to delete it for make it disabled, right?

If we assume that we want to loop on several plugins, it could be nice to be
able to set an ordered stack of authentication modules. This could allow us to
chose which one is used first etc... In this case we need a dedicated page in

You are receiving this mail because:
You are watching all bug changes.
Koha-bugs mailing list
website :
git :
bugs :

Reply via email to