Versions Compared

Old Version 30

changes.mady.by.user Peter Brand

Saved on

compared with

New Version 31

changes.mady.by.user Peter Brand

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: SPs can interfed, too

...

  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) your SP aims to support, where applicable.
  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 description
  5. The URL to the Privacy Policy covering this service. See Privacy policy guidelines for Service Providers for more.
  6. An HTTPS URL referencing a logo for the service (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 (optional; depends on target audience of the service)

Identity Providers

For the registration of a SAML Identity Provider (IDP) within eduID.at please provide the following information:

  1. Whether the IDP supports the following:
    • Service Categories (both REFEDS R&S and GÉANT CoCo strongly recommended)
    • persistent NameIDs (optional)
  2. The preferred display name for the organisation in German and English language (if differing from what the organisation's web site shows)
  3. Functional/role email address(es), not personal one(s) – possibly re-using the same address for all roles – and display names for:
    • the IDP's technical contact
    • the support contact (optional)
    • the security contact (optional, but recommended)
  4. HTTPS URLs referencing:
    • A logo for the organisation (PNG format), between 80 and 250 pixels in size (either dimension)
    • A "favicon"-style icon (16×16 pixel)
  5. Whether you intend to also participate in Interfederation/eduGAIN (strongly recommended)