Page History

...

1. What attributes the service needs in order to function properly and what they are used for. Additional attributes not strictly needed for the service (but which may provide for a better user experience if available) may be listed separately, clearly indicating their optional status. See What attributes are relevant for a Service Provider for guidance.
2. Which of the common Service Categories (REFEDS R&S and/or , GÉANT CoCo v1, REFEDS CoCo v2, etc.) your SP aims to support, where applicableclaims to support.
   N.B.: SPs without support for any of the (community-)standard Service Categories will experience failed log-in attempts due to IDPs not releasing attributes – unless the SP has leverage to convince IDPs otherwise, e.g. by managing "trust" via contracts anyway or by having special political power or legal standing.
3. A display name and short (1 paragraph max.) description of the service (in English and/or German)
4. A functional/role email address (and optional display name) – not a personal one – for the technical contact to be published with the SAML entity.
5. The URL to the Privacy Policy covering this service. See Privacy Notice template document for Service Providers for more.
6. An HTTPS URL referencing a logo for the service (in PNG format), between 80 and 250 pixels in size (either dimension).
7. How you intend to implement IdP Discovery. While you may use the fallback SAML Discovery Service(s) provided by ACOnet it's preferrable to integrate discovery with your service, in order to provide for a more consistent user experience, cf. the REFEDS Discovery Guide.
8. Whether you intend to also participate in Interfederation/eduGAIN (only makes sense if the target audience of the service also includes members of academic institutions outside Austria.)

...