Versions Compared

Old Version 4

changes.mady.by.user trscavo@internet2.edu

Saved on

compared with

New Version 5

changes.mady.by.user trscavo@internet2.edu

Saved on

Key

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

...

At this point, only a small subset of InCommon metadata is included in the Export Aggregate.

InCommon Operations will begin exporting metadata at scale on February 15, 2016. At that time, all IdP metadata will be exported by default. All SPs that have explicitly opted in will be exported as well. Site Administrators choose whether or not to export metadata via the Federation Manager.
Infonote
titleFull eduGAIN participation begins on February 15, 2016
Export Recommendations and Options

InCommon recommends the following options:

  1. IdP operators SHOULD export IdP metadata to eduGAIN. Eventually, we expect all IdP metadata to be exported to eduGAIN except those few IdPs that do not satisfy InCommon’s export policy rules. See the Interfederation Technical Policy document in the wiki for more information.
  2. An SP owner SHOULD export SP metadata to eduGAIN if the deployment intends to interoperate with global IdPs. An SP deployment that interoperates with InCommon IdPs only SHOULD NOT export its metadata to eduGAIN.

To adjust your export option, log into the Federation Manager and then click "IdP Metadata Wizard" or "SP Metadata Wizard" as appropriate. Simply edit the metadata and check the box to indicate your choice.

 

Code Block
languagebash
# InCommon export aggregate distribution point
$ MD_LOCATION=http://md.incommon.org/InCommon/InCommon-metadata-export.xml

# Fetch the metadata and list the entityIDs of exported entity descriptors
$ MD_PATH=/tmp/InCommon-metadata-export.xml
$ curl --silent $MD_LOCATION \
    | tee $MD_PATH \
    | grep -F ' entityID=' \
    | sed 's/^.* entityID="\([^"]*\).*$/\1/'