Versions Compared

Old Version 18

changes.mady.by.user Teun Fransen

Saved on

compared with

New Version 19

changes.mady.by.user Thijs Kinkhorst

Saved on

Key

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

...

  1. Be sure that your service is configured in SURFconext (Production or Test environment).
  2. Request a metadata file with all IdPs that have been coupled with your service (the file "SURFconext IdPs metadata"  at https://enginemetadata(.test).surfconext.nl/authentication/proxy/idps-metadata?sp-entity-id=SP-ENTITY-ID
    1. This contains all IdPs on the platform. You can also request a version that is scoped to your Service Provider: that only lists the IdPs connected to your SP, and will be updated automatically when this list changes. Request that from support@surfconext.nl
    : replace SP-ENTITY-ID with your EntityID as found in your metadata).You will receive a file with 1) your own SP metadata and (2) metadata of all IdPs that have have been coupled with your service
    1. .
  3. Configure the metadata into your Service Provider directly or use it (e.g. with Xpath) to extract the Display names and SSO locations of the IdPs to be shown on your WAYF.
    The SSO location points to a SURFconext endpoint and has a specific identifier at the end. This identifier enables SURFconext to forward the authentication request to the requested IdP.

...