Versions Compared

Old Version 20

changes.mady.by.user Stephen Lovell

Saved on

compared with

New Version 21

changes.mady.by.user Stephen Lovell

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

InformationDescription
entityIDThe SAML entityID must be an HTTPS schema based. See https://github.com/REFEDS/MRPS/blob/v1/mrps.md#52-entityid-format and https://spaces.at.internet2.edu/display/InCFederation/Entity+IDs
SAML Metadata

A URL to the XML metadata (preferred), or an XML metadata file. This file/URL should be valid SAML metadata containing at least the following elements:

  • "contacts"
    • one technical contact (for dealing with authentication/security/privacy issues)
    • one support contact (for generic application support questions)
  • "name" <= a very short name to be shown in user interfaces, for instance "GÉANT Intranet"
  • An X.509 certificate for signing requests
Service description

Longer descriptive text with at least:

  • The purpose of the service
  • Its intended audience
  • Its status (production, testing, etc)
  • The date it went into production
  • The software it runs
Service URLThe actual URL to the main service, for instance https://intranet.geant.org.
Contacts

Support Contact and Administrative Contact information

For each please provide:

Given name

Last name

Email address





Supplied information


The SAML proxy will always provide the following attributes to its downstream services:

...