InCommon Operations Notifications

[Thomas Scavo <>]

FYI

Phase 3 of the Roadmap for Operationalizing eduGAIN [1] is now complete.

At 12:38 pm ET today, Ops imported eduGAIN metadata into the InCommon main 
production aggregate. Subsequently the metadata was published to the backup 
metadata server, checked for accuracy, and then synced with the primary 
metadata server. FYI a snapshot of the InCommon metadata aggregates [2] has 
been recorded in the wiki.

At more-or-less the same time, a new export aggregate was created, including 
402 IdPs and 70 SPs. These entities have been incorporated directly into the 
eduGAIN aggregate, as you can see by browsing the eduGAIN web site. [3]

We are now LIVE with the global eduGAIN service!

Tom Scavo
for InCommon Operations

[1] https://spaces.internet2.edu/x/8gKDBQ
[2] https://spaces.internet2.edu/x/-IGeBQ
[3] https://technical.edugain.org/status

________________________________________
From: Thomas Scavo
Sent: Tuesday, February 2, 2016 4:45 PM
To: 

Cc: InCommon Administration
Subject: Getting Ready for eduGAIN [ACTION REQUIRED]

You are receiving this message because you are an InCommon Federation Site 
Administrator or are otherwise subscribed to this mailing list. Please widely 
redistribute this message inside your organization as needed.

On February 15, InCommon Operations begins full integration with the global 
eduGAIN [1] service. To protect against failed metadata processes [2] and to 
ensure the continued operation of all federation services, your ACTION MAY BE 
REQUIRED now. For detailed instructions, consult the comprehensive Getting 
Ready for eduGAIN [3] wiki page.

The following operations will commence on February 15:

1. InCommon Ops will begin importing eduGAIN metadata into the main 
production aggregate, which will cause the overall size of InCommon metadata 
to grow from 17MB to over 32MB

2. InCommon Ops will begin exporting metadata to eduGAIN at scale
  2a. Your InCommon IdP metadata will be exported by default
  2b. Your InCommon SP metadata will be exported on demand

Be aware that the following deployments are AT RISK:

- All simpleSAMLphp deployments (both SP and IdP). The metarefresh module 
that ships with the simpleSAMLphp software is known to be sensitive to large 
metadata files. Deployers are advised to upgrade to simpleSAMLphp v1.13.2 (or 
later) ASAP.

- All Shibboleth IdP deployments. All versions of the Shibboleth IdP software 
are known to be sensitive to large metadata files. Deployers are advised to 
allocate at least 1024MB of heap in the JVM.

If you have questions or concerns, please write to 


Tom Scavo
for InCommon Operations

[1] eduGAIN https://spaces.internet2.edu/x/X4BdBQ
[2] Protect Against Failed Metadata Processes 
https://spaces.internet2.edu/x/zgFwBQ
[3] Getting Ready for eduGAIN https://spaces.internet2.edu/x/VASDBQ