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 Attribute release
Created by Guest
Created on Jun 3, 2026

Scope EPPN when it is used as SAML NameID attribute

We followed instructions to create EPPN attribute via local connector and it is scoped when released as urn:oid:1.3.6.1.4.1.5923.1.1.1.6, however our service provider requires the EPPN value to be mapped as SAML NameID and it is then released unscoped. It would be good if EPPN can be scoped for SAML NameID too OR allow urn:oid:1.3.6.1.4.1.5923.1.1.1.6 to be mapped as SAML NameID instead (it does not appear in dropdown menu currently).
As background - we do not receive an EPPN value equivalent from Azure directly as it is based on a former UPN format that has since been changed, we need the value to match the older format as it is used for a service provider that offers personalisation. We do receive another attribute that is the unscoped version and so was hoping to be able to use EPPN to do this since you cannot transform using the value from another attribute + free text (I will put in another idea for this functionality).

Is this currently impacting your ability to use OpenAthens effectively? Yes
Idea type Day-to-day tasks/actions improvements, Something new
  • Attach files