Page History
...
Adjust the IDP configuration to lookup and/or generate any missing attributes. You'll find copy/paste-able examples for all of those in our IDP 3 4 Attribute resolution documentation.
| Note |
|---|
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.
| Info |
|---|
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 eduGAIN. |
Test Be sure to test your attribute release rules with the eduGAIN Attribute Release Check!
| Tip |
|---|
There are more useful tests available in our Testing an IDP documentation. |
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 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 sometimes find themselfs unable to access some of these services, going forwardeven if the IDP would release the needed attributes.
Overview
Content Tools
Tasks