For large organisations and consortia who need the proxy service to present different IP addresses for different parts of their account structure we have an option available where the OpenAthens Managed Proxy Service can use a locally hosted forward proxy to perform the final hop to the publisher site.
OpenAthens still does the complicated parts (selecting the relevant configurations, permissions, redirector support and re-writing), but the final hop to the resource can come from an IP address of your own - i.e. one that vendors already have registered for you. Wait... what? Why would..?
As discussed on the about the managed proxy service page, this kind of proxy is a rewriting proxy and whilst the reverse proxy and rewriting parts have to sit with us, the forward proxy part that is the last step between the user and the content doesn't have to and this opens up some possibilities:
- You can host the forward proxy within your own network where it appears at one of your own IP addresses - you wouldn't have to supply new addresses to publishers
- Depending on where in the world you are there can be some performance improvements - e.g. where you are geographically closer to the website than we are
- You can use different IP addresses for different parts of your organisation
In a sense you are bringing your own IP address to the managed proxy service whilst OpenAthens still does the complicated parts (selecting the relevant configurations, permissions, redirector support and re-writing).
There are three options documented.
For the smaller organisations who just want the to use their own IP elementaddress:
- Single tenant use of Squid with OpenAthens
- Single tenant use of Squid as a forward proxy on Windows (coming soon)