inc-ops-notifications - [InCommon NOTICE] importing/exporting eduGAIN metadata [ACTION REQUIRED]

Subject: InCommon Operations Notifications

List archive

[InCommon NOTICE] importing/exporting eduGAIN metadata [ACTION REQUIRED]

From: Thomas Scavo <>
To: "" <>
Cc: InCommon Administration <>
Subject: [InCommon NOTICE] importing/exporting eduGAIN metadata [ACTION REQUIRED]
Date: Tue, 7 Jun 2016 14:17:33 +0000
Accept-language: en-US
Authentication-results: spf=none (sender IP is ) ;
Spamdiagnosticmetadata: NSPM
Spamdiagnosticoutput: 1:99

You are receiving this message because you are an InCommon Site Administrator
or have otherwise subscribed to this mailing list. Please distribute this
message to your delegated administrators and other technical contacts as
needed. Your ACTION MAY BE REQUIRED.

CONTENTS
Importing eduGAIN Metadata: For all
Importing eduGAIN Metadata: For IdP deployers
Importing eduGAIN Metadata: For SP deployers
Exporting eduGAIN Metadata: For all
Exporting eduGAIN Metadata: For IdP deployers
Exporting eduGAIN Metadata: For SP deployers
Attachment: Entities_export_status_2016-06-07.pdf
Attachment: entities-in-multiple-federations-2016-06-07.txt

----
Importing eduGAIN Metadata: For all

In response to an incident that occurred on March 21, 2016, a more robust
metadata import and signing process has been deployed. See the Metadata
Import and Signing topic in the wiki for details:
https://spaces.internet2.edu/x/uQjcBQ

Imported metadata is filtered as outlined on the Interfederation Technical
Policy wiki page: https://spaces.internet2.edu/x/TgCNBQ

A copy of the import filter log is routinely published on the web server:
https://wayf.incommonfederation.org/metadata-diff/md_filter_reports/?C=M;O=D

On Monday, June 13, 2016, InCommon Ops will deploy four (4) additional filter
stages in production. See the Interfederation Technical Policy wiki page
(linked above) for details. Watch the published import filter log (linked
above) for changes.

Importing eduGAIN Metadata: For IdP deployers

IdP deployments SHOULD NOT filter metadata. If you do, please self-assert the
hide-from-discovery entity attribute. For instructions, see the Hide From
Discovery Category topic in the wiki: https://spaces.internet2.edu/x/6YD4Ag

TIP. If you are unable/unwilling to release attributes to global SPs, adjust
your attribute release policy, not your metadata intake. For instructions,
visit the wiki topic on the Registered By InCommon Category (and its child
page): https://spaces.internet2.edu/x/eQ07BQ

Importing eduGAIN Metadata: For SP deployers

SPs assume more risk than IdPs, so filtering metadata remains an option for
SPs (albeit a rather severe option). For recommendations, visit the wiki
topic on the Registered By InCommon Category (and its child page):
https://spaces.internet2.edu/x/eQ07BQ

TIP. Instead of filtering metadata, consider filtering IdPs from the
discovery interface. See the above wiki page for details.

Exporting eduGAIN Metadata: For all

For reference, visit the Export Aggregate wiki page:
https://spaces.internet2.edu/x/vACVBQ

Exporting eduGAIN Metadata: For IdP deployers

IdP operators SHOULD export their metadata to eduGAIN (which is the default).
If you operate one of the 24 IdPs that have opted out of eduGAIN (see the
attached PDF), please reconsider your options by logging into the Federation
Manager and checking the box to export.

NOTE. Eventually we expect all IdP metadata to be exported to eduGAIN except
those few IdPs that do not satisfy InCommon’s export policy rules. For
details, see the Interfederation Technical Policy document in the wiki:
https://spaces.internet2.edu/x/TgCNBQ

Exporting eduGAIN Metadata: For SP deployers

An SP owner SHOULD export SP metadata to eduGAIN if the deployment intends to
interoperate with global IdPs. An SP that interoperates with one or more
InCommon IdPs *only* SHOULD NOT export its metadata to eduGAIN. If you own an
SP that is exporting its metadata unnecessarily, please reconsider your
options by logging into the Federation Manager and checking the box NOT to
export. For a complete list of SPs that are exporting their metadata to
eduGAIN, see the attached PDF.

Dozens of InCommon SPs are registered in multiple federations (see attached
TXT file). This has both advantages and disadvantages. If you are the owner
of such an SP, and you’d like to discuss your options, please contact us at

----
Tom Scavo
For InCommon Operations

Attachment: Entities_export_status_2016-06-07.pdf
Description: Entities_export_status_2016-06-07.pdf

[InCommon NOTICE] importing/exporting eduGAIN metadata [ACTION REQUIRED], Thomas Scavo, 06/07/2016

List archive

[InCommon NOTICE] importing/exporting eduGAIN metadata [ACTION REQUIRED]