Move API management into Alma admin functional area
Management of APIs is currently managed via the developers network portal, which does not support institutional SSO, and barely supports MFA (email-only tied to one email address).
Moving the management of the Alma/Exlibris APIs into the Alma/LMS admin interface would bring the management of the Exlibris APIs into an environment that supports SSO and more granular permissioning in line with current Exlibris/Alma best practice, and ensure access is consistent with each institutions authentication/authorisation requirements. This would also require Exlibris to create roles specifically for API management/administration.
This would provide a more secure and better experience for Exlibris customers, and provide a consistent UI experience. It would also ensure that provisioning of access to institutional APIs is managed by the institution itself
Matthew Hooper
shared this idea
-
Alevtina (Allie) Verbovetskaya
commented
Supporting this strongly from CUNY's perspective. As a consortium running Alma across 26 institutions via 22 IZs, the Developer Network portal creates real security and administrative gaps for us.
Granular role-based access within Alma would let us distinguish between staff who use integrations and those who administer API credentials—a distinction the current portal doesn't support. At CUNY, where we're actively expanding programmatic access to Alma to support library automation and AI-assisted workflows, this matters more every month.
There's no good reason API management should live outside the environment that already handles sensitive configuration with appropriate controls.
This is a security, governance, and usability improvement rolled into one. Strongly in favor.