Support for e-resource proxies and url customisers
Description
Priority
Labels
Fix versions
None
Development Team
Bienenvolk
Assignee

Parent
None
Attachments
4
100% Done
defines
has to be done after
relates to
Checklist
hideTestRail: Results
Activity
Show:

Ethan Freestone November 16, 2020 at 5:09 PM
Comment made on 1048 with StringTemplate document and branch:
https://folio-org.atlassian.net/browse/ERM-1048?focusedCommentId=90145&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel

Owen Stephens September 14, 2020 at 2:41 PM
Done
Details
Details
Reporter

TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created September 8, 2020 at 2:00 PM
Updated November 30, 2020 at 10:45 AM
Resolved November 30, 2020 at 10:45 AM
TestRail: Cases
TestRail: Runs
Some institutions run "proxy servers" (aka "reverse proxies") which are used to proxy requests for eresources in order that a user can access the e-resource with minimal authentication/authorisation issues (e.g. if the proxy server is granted IP authorisation to the resource, the user can access the resource from any location using the proxy server)
There are a variety of proxy servers commonly used by libraries. The most common is probably EZProxy, but there are a number of commercial services as well as homegrown and open source solutions.
This story is to implement support for adding multiple proxy server configurations to a tenant and then including "proxied" URLs in displays and exports.
In order to implement support for proxy servers we will need to:
Add support for proxy server configurations (including building proxied URLs)
Add UI for managing proxy server configurations
Include proxied URLs in exports
Include proxied URLs in UI where appropriate