InCommon Operations Notifications

[Tom Scavo <>]

You are receiving this note as a followup to the message quoted below.
Your ACTION IS REQUIRED.

A new metadata signing certificate and three new metadata aggregates
have been deployed. See the Phase 1 Implementation Plan of the
Metadata Distribution Working Group for links and details:
https://spaces.internet2.edu/x/5IOZAg

All SAML deployments in the InCommon Federation are required to
migrate to one of the new metadata aggregates as soon as possible but
no later than March 29, 2014. See the Phase 1 Implementation Plan FAQ
for specific migration instructions:
https://spaces.internet2.edu/x/yoCkAg

If you have questions, or just want to find out more, we encourage you
to subscribe to our new mailing list:

Mailing list: 


We look forward to hearing from you!

----
InCommon Operations


On Wed, Dec 4, 2013 at 8:57 AM, Tom Scavo 
<>
 wrote:
> You are receiving this message because you are a site administrator
> for the InCommon Federation. No action is required at this time.
>
> On December 18th, InCommon Operations will deploy three new metadata
> aggregates on a new vhost (md.incommon.org). All SAML deployments will
> be asked to migrate to one of the new metadata aggregates as soon as
> possible but no later than March 29, 2014. In the future, all new
> metadata services will be deployed on md.incommon.org. Legacy vhost
> wayf.incommonfederation.org will be phased out.
>
> An important driver for switching to a new metadata server is the
> desire to migrate to SHA-2 throughout the InCommon Federation. The end
> goal is for all metadata processes to be able to verify an XML
> signature that uses a SHA-2 digest algorithm by June 30, 2014. For
> details about any aspect of this effort, see the Phase 1
> Implementation Plan of the Metadata Distribution Working Group:
> https://spaces.internet2.edu/x/5IOZAg
>
> Each SAML deployment in the Federation will choose exactly one of the
> new metadata aggregates. If your metadata process is not SHA-2
> compatible, you will migrate to the fallback metadata aggregate.
> Otherwise you will migrate to the production metadata aggregate or the
> preview metadata aggregate, depending on your deployment. For more
> information about metadata aggregates, see:
> https://spaces.internet2.edu/x/SoG8Ag
>
> To find out more, subscribe to our new mailing list and/or check out our 
> FAQ.
>
> Mailing list: 
> 
> FAQ: https://spaces.internet2.edu/x/yoCkAg
>
> ----
> InCommon Operations