We support proxy, why do I need OpenAthens?

Our resource hub is full of educational content and raises awareness of the three key issues around IP-based access: security, poor user experience, and lack of personalization.

Laptop next to notepad

The problem with IP-based access

Problems with IP authentication

John Felts explains the difficulties with using IP-based access in today’s modern world.  John is head of information technology and collecations at Kimbel library, Coastal Carolina University and a member of the SeamlessAccess organisation.

Two people at a whiteboard explaining a diagram
Knowledge icon white

IP proxy or OpenAthens?

The way we all use technology has dramatically evolved since the current access methods were designed.

Our handy guide explains the key differences between IP proxy and OpenAthens single sign-on technology.

IP vs OpenAthens guide

How our technology is more secure

Killing two birds with one stone: Beating the pirates and giving users the experience they deserve

Sari Frances, director of content protection services at Elsevier, explains how federated single sign-on technology like ours helps to combat piracy.

Proxy. Woman working on laptop with poor user experience

Why proxies deliver a poor user experience

Our e-resources manager Emma Wilson-Shaw explains why proxies deliver a poor remote access experience.

Read our blog

Researchers want a better user experience

Man working from home

How federated access delivers seamless remote access

Ralph Youngen, senior director of technology strategy & partnerships at the American Chemical Society, recounts his company’s experience of seamless remote access during the global pandemic.

Read Ralph's blog on Scholarly Kitchen
Woman browsing the internet

Federated access increases resource usage

Our blog explains why a good user experience boosts resource usage and gives users secure, remote access to library resources.

Read our blog about federated access
Three students researching online

Work with us to deliver a great UX

We support NISO standards and work with the SeamlessAccess service to make user login easy. Hear how IOP Publishing helped test our integration with SeamlessAccess to create an improved user journey to IOP Science.

 

How IOP Publishing simplified user access to IOPscience

Your customers care about privacy

Protecting personal data

The University of Surrey describe their experiences of challenging publisher requests for users personal data. They provide examples of three suppliers, and the outcomes they achieved.

Challenges of providing personalization

With IP-based access, users need to set up separate accounts with every publisher to access their search history, favorites and recommended content. Peter Reid at Bath Spa University explains that a balance needs to be struck between usability and privacy.

Privacy vs Personalization

Our popular Access Lab 2020 panel debate explores some of the issues around privacy and personalization. Speakers share their ideas on how we can improve our service offer to researchers and students, wherever they are in the world.

Supporting your business needs

Two people signing a licence agreement

Flexible licence agreements

Our standards-based software gives you the flexibility to offer licenses based on organization, department or individual and the ability to scale up to a global customer-base.

Student using computer

Product development based on user insights

Discover more about how learners and researchers are using and engaging with your content so you can develop relevant services they’ll benefit from.

Student personalising their online experience

Personalization that is privacy preserving

Library patrons also benefit from personalization features such as favorites, saved searches and annotated content which is not possible with IP recognition.

Next steps

Book a demo to find out why OpenAthens single sign-on beats IP-based solutions hands down.

We will use your contact details to respond to your request.
View our privacy policy to find out more.

All required fields are marked with '*'

  • This field is for validation purposes and should be left unchanged.