You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Library services, databases and academic content providers still use IP addresses (and often IPv4 only) for mapping "users" (network addresses, really) to contracts. There is little we can do today to change this other than to engage with every publisher on the planet to request and help them with integrating identity federation technology. All content providers are encouraged to (and in many cases already do) base authorization of individuals accessing their resources on attributes (i.e., data about the user or her institution) transmitted via identity federation protocols (today SAML 2.0+).

In most cases the only information required by a content provider will be an attribute detailing whether an individual is covered by an existing contract. (Sometimes an identifier unique to the subject will also be required and will allow the service provider to also add personalized services, e.g. storing of search results or documents).
The absence of such authorization data in a response from the issuer (the Identity Provider) of course means that according to the issuer the subject requesting access is not entitled to the resource. Consequently Attribute Based Access Control (ABAC) means the service provider needs to actually check for those attributes and deny access if the agreed-upon attribute value was not been provided in the response.

There is no other way for an institution to signal whether an individual should be entitled to a resource or not. Authentication at an academic institution does not mean the subject is necessarily authorized to access licensed resources on behalf of that institution.

The eduPerson specification has defined the generic attribute eduPersonEntitlement to communicate entitlements, permissions or rights between entities. For the specific case of library services MACE-Dir has then defined a standard eduPersonEntitlement attribute value. This is the only attribute (other than maybe a unique identifier) library services will generally need, as such no more data should be sent from the Identity Provider:

common-lib-terms Entitlement

(Due to some fallout after a website reconstruction at Internet2 the defintion of the common-lib-terms Entitlement value is currently inaccessible. Thankfully archive.org has an older copy of that specificiation. Please see that for the semantics of that attribute.)

"Friendly" attribute nameFormal SAML2 attribute name (on-the-wire)Attribute value string
eduPersonEntitlementurn:oid:1.3.6.1.4.1.5923.1.1.1.7urn:mace:dir:entitlement:common-lib-terms

The NameFormat (what format is the the formal attribute name in) is always "urn:oasis:names:tc:SAML:2.0:attrname-format:uri". For legacy protocol versions (SAML1.x) the formal attribute name is "urn:mace:dir:attribute-def:eduPersonEntitlement" instead. See https://eduid.at/entities/sp and "mouse-over" the attribute name to find out its required formal name.

  • No labels