|
Large, complex libraries seeking a managed access management service that provides greater visibility and control, minimizes operational complexity, and supports both federated authentication and proxy-based access.Â
|
Institutions looking for access to licensed content through a proxy-based model.Â
|
Organizations looking for federated authentication, want maximum control, and with the resources and expertise to manage their own infrastructure.Â
|
|
Centralised, web-based administration portal that enables administrators to manage user access, resources, and authentication settings from a single interface.
|
Provides an administration interface with control over proxy configuration, database stanza management, security settings, and troubleshooting. Admin may require technical expertise.
|
Administration often requires specialist technical knowledge and direct management of configuration files, metadata, and identity integrations.
|
|
Built-in centralized identity and access management capabilities, allowing administrators manage user attributes and groups in one place. It can also integrate with external identity systems for user management.
|
Typically relies on external identity systems for user management, while EZproxy provides authentication and access control through its user.txt-based configuration.
|
No native user directory. User identities and attributes are typically managed in external identity systems and surfaced through Shibboleth for authentication and access control.
|
|
Advanced reporting. Analyse resource usage across user groups and other attributes. Interactive dashboards and visualizations make it easy to identify trends and support evidence-based decisions.
|
Basic reporting. Access logs and basic usage reporting help administrators monitor resource access. Advanced analytics require a separate subscription.
|
Limited native reporting. Authentication and audit logs are available, but additional tools are typically needed to generate detailed usage reports and analytics.
|
|
Privacy-preserving federated authentication with control over attribute release. User identities remain under institutional control, and will only be released to service providers if agreed by the institutional admin.
Access decisions are based on the user’s identity rather than their location or IP address.
|
Security is delivered through a proxy-based model integrated with institutional authentication systems.
|
Privacy-preserving federated authentication with control over attribute release. User identities remain under institutional control, and will only be released to service providers if agreed by the institutional admin.
Access decisions are based on the user’s identity rather than their location or IP address.
|
|
Dedicated onboarding and account manager.
|
Self-hosted: The institution installs, hosts and maintains EZproxy on its own IT infrastructure.
Hosted: Fully managed by OCLC.
|
Self-managed.
|
|
Low. Centralised administration and personalised support from onboarding through to day-to-day operations help reduce the need for specialist expertise.
|
Typically requires familiarity with proxy configuration, resource settings and troubleshooting.
|
High. Deployment and ongoing maintenance typically require expertise in identity management, SAML federation, and infrastructure management. As an open-source solution, it primarily relies on documentation rather than a dedicated vendor-managed support service.
|
|
Subscription-based pricing. Lower operational overhead through a managed service, with less infrastructure to maintain in-house.Â
|
Subscription-based. Organizations using self-hosted EZproxy may incur additional operational costs related to infrastructure, maintenance, and administration.
|
No software licensing fees for the open-source platform, but specialist staffing, infrastructure and ongoing maintenance can contribute to operational costs.
|