Details
-
Story
-
Status: Closed (View Workflow)
-
TBD
-
Resolution: Done
-
-
ERM Sprint 97, ERM Sprint 98, ERM Sprint 99, ERM Sprint 102
-
Bienenvolk
Description
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
TestRail: Results
Attachments
Issue Links
- defines
-
UXPROD-1759 Agreements | Local KB | Support adding custom data to URLs for resources in Agreements
-
- Closed
-
- has to be done after
-
ERM-1048 Implement "template" mechanism to create URLs for resources based on existing data
-
- Closed
-
- relates to
-
ERM-1242 Frontend tests for URL customisation in RTL
-
- Closed
-
-
ERM-1110 Add templated URLs to PCI display
-
- Closed
-