http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13485 Kyle M Hall <kyle@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kyle@bywatersolutions.com --- Comment #12 from Kyle M Hall <kyle@bywatersolutions.com> --- (In reply to David Cook from comment #8)
(In reply to Eric Bégin from comment #7)
David,
You are correct. The proxy page is used for ressources that are restricted to connected users.
The main usage is to allow patrons to access resources available by providers using a HTTP Referer mechanism.
Note : This implementation doesn't include any password mechanism. Adding it would be possible. Borrowers attributes could be use to manage the username / passwords. For exemple, user accessing proxypage.pl?id=ebsco could look at ebscoUsername and ebscoPassword attributes.
Thanks for confirming, Eric :).
I might take a look at adding that later down the track, depending if we have anyone needing it. We have a client or two who are looking at something along these lines, but nothing has been 100% decided yet.
To make this more extensible, we could simply evaluate the ProxyPageContent pref as TT, and then one could take advantage of all the TT plugins such as Koha.Preference. -- You are receiving this mail because: You are watching all bug changes.