Considerations for eduID.at SAML Identity Providers for use with services registered with other Identity Federations via Interfederation arrangements (such as eduGAIN).
You will find that nothing here is specific to Interfederation participation, i.e. all IDPs in eduID.at should be configured like this.
Only by (also) participating in Interfederation will you be able to support your academic constituency in providing them with secured access to the resources they need. For example E-research cannot happen without international collaboration and shared, properly managed access to scientific tools. Cf. the FIM4R (Federated Identity Management for Research Collaborations) paper.
All IDPs in eduID.at should 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, so can replace any previously used one:
As always, use the provided Metadata Verification Key to make sure the metadata is authentic and hasn't been tampered with.
Adjust the IDP configuration to lookup and/or generate any missing attributes.
Every eduID.at-registered IDP should be able to produce at least the following attributes:
Extend your existing IDP attribute release configuration to make use of Service Categories, to enable automated, scalable and controlled attribute release.
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.
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 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 to make available for login. By only listing IDPs that 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! Conversely, IDPs not announcing support for any of the popular Service Categories (i.e., those giving the Service Providers no indication that necessary attributes will be released) might find themselfs unable to access some of these services, going forward.