Skip to Main Content
OpenAthens Ideas Portal

We're always looking for ways to improve our products, and we'd love your input to help us make that happen. Your suggestions will guide us in deciding where we should focus our future research and development.

Just sign in with your email to share your thoughts or vote for ideas you like—it'll help them get noticed!


Here’s how the portal is organised:

  • Librarians (Identity Providers): Share ideas that help organisations that manage user identities and provide access to online content and services. This includes improving the experience for students and researchers.

  • Publishers (Service Providers): Share ideas for organisations that offer content and services.


Guidance on using this portal

Status Feedback wanted
Workspace Librarians
Categories Accessing resources
Created by Guest
Created on Nov 16, 2026

Enhancement Request: Support for SirsiDynix Web Services Authentication Endpoint /symws/user/patron/login

Background

During a recent OpenAthens implementation project for a customer using SirsiDynix Symphony, we identified a compatibility issue in the existing OpenAthens SirsiDynix connector: https://docs.openathens.net/libraries/sirsidynix-connector.

Based on information provided by OpenAthens Support, the current connector attempts authentication using the legacy endpoint:
/symws/rest/security/loginUser?includeUserMiscInfo=true
This endpoint is associated with older versions of SirsiDynix Web Services (WS 4.0).
However, many Symphony environments are now using newer versions of SirsiDynix Web Services, where patron authentication is performed through:
/symws/user/patron/login
using JSON payloads and mandatory headers such as:

- x-sirs-clientID
- SD-Originating-App-Id

Problem

In the investigated environment:

- direct authentication against /symws/user/patron/login succeeds and returns a valid session token;
- OpenAthens authentication fails because the connector continues to call the legacy /symws/rest/security/loginUser endpoint;
- OpenAthens logs provided by Support confirm attempts to connect to the legacy endpoint rather than the newer authentication API.

This creates a compatibility gap for customers running current SirsiDynix Symphony installations and may prevent successful deployment of OpenAthens local-directory authentication.

Requested Enhancement

Please consider enhancing the SirsiDynix Symphony connector to support modern SirsiDynix Web Services authentication methods.
Possible approaches could include:

1. Support for the /symws/user/patron/login endpoint as an alternative authentication mechanism.
2. A configurable option allowing administrators to choose between:
- legacy authentication (/symws/rest/security/loginUser)
- modern authentication (/symws/user/patron/login)
3. Automatic detection of the available Symphony Web Services version and selection of an appropriate authentication workflow.

Example Case

During testing, successful authentication was confirmed via direct calls to:
https://sym8web.p.lodz.pl/symws/user/patron/login
while OpenAthens support logs showed the connector attempting to use:
https://sym8web.p.lodz.pl/symws/rest/security/loginUser?includeUserMiscInfo=true
demonstrating the current endpoint mismatch.

Thank you for considering this enhancement.

Is this currently impacting your ability to use OpenAthens effectively? Yes
  • Attach files