Preparing an IDP for Interfederation

Considerations for SAML Identity Providers for use with services registered with other Identity Federations via Interfederation arrangements (such as eduGAIN).

Metadata

IDPs in eduID.at can always load SAML Metadata that also includes entities known via Interfederation agreements, such as eduGAIN. This metadata set alone is sufficient for all eduID.at Federation and Interfederation purposes:

As always, use the provided Metadata Verification Key to make sure the metadata is authentic and hasn't been tempered with.

Make attributes available

Adjust the IDP configuration to lookup and/or generate any missing attributes.

• Name attributes
  • displayName (urn:oid:2.16.840.1.113730.3.1.241)
  • givenName (urn:oid:2.5.4.42)
  • sn/surname (urn:oid:2.5.4.4)
• Identifiers
  • eduPersonTargetedID (a.k.a. SAML2 persistent NameID, urn:oid:1.3.6.1.4.1.5923.1.1.1.10)
  • eduPersonPrincipalName (urn:oid:1.3.6.1.4.1.5923.1.1.1.6)
  • mail (urn:oid:0.9.2342.19200300.100.1.3)
• Authorization
  • eduPersonScopedAffiliation (urn:oid:1.3.6.1.4.1.5923.1.1.1.9)
  • eduPersonEntitlement (urn:oid:1.3.6.1.4.1.5923.1.1.1.7)
• Organizational data
  • schacHomeOrganization (urn:oid:1.3.6.1.4.1.25178.1.2.9)

Attribute release

Extend your existing IDP configuration to scalably release needed attributes to appropriate Service Providers.
The use of the provided Service Categories to automate attribute release as much as possible is recommended for all eduID.at IDPs, especially those also participating in Interfederation.

Notify ACOnet

To make your Identity Provider usable with services registered in other federations contact ACOnet in order for your entity to become visible to those interfederation services.

If you added support for Service Categories-based attribute release (which is strongly recommended!) please also notify ACOnet about which ones you support, so this can be documented in your Identity Provider's SAML Metadata. Signalling the support for a given Service Category allows services relying on attributes defined in such Service Categories to automatically filter which IDPs they make available for login. By only listing IDPs who claim to support a given Service Category chances of successful logins (and hence of a proper user experience) for subjects coming from those Identity Providers are greatly enhanced!