InCommon Operations Notifications

[David Shafer <>]

The issue involving the InCommon Federation Manager has been resolved, and 
the system is working normally again.

Following a problem during a routine upgrade last night, June 27, we had to 
restore the Federation Manager database using a backup from Tuesday, June 26, 
2018, at 6:30 p.m. U.S. Eastern Time. This morning we discovered additional 
problems and had to repeat the database restoration.

After confirming the restoration completed successfully, we identified 
thirteen entities having changes that had been published in metadata before 
the upgrade on June 27, but had not been captured in the database backup from 
June 26. Where those changes involved critical functional elements (including 
new entities, changes to signing certificates, and new ACS endpoints), 
InCommon staff applied the changes and notified the relevant site 
administrators. Where the changes involved only informational elements 
(contacts, logo and privacy URLs), InCommon staff contacted the relevant site 
administrators to coordinate next steps.

We'll share a complete after-action report (including steps we're taking to 
prevent similar problems in the future) at a later date.

If you have any questions or concerns, please contact InCommon Support at 
.

Thank you,

David Shafer
DevOps Manager,
Internet2 Trust & Identity


-----Original Message-----
From: 
<>
 on behalf of David Shafer 
<>
Date: Thursday, June 28, 2018 at 10:40 AM
To: 
""
 
<>
Subject: [InCommon NOTICE] Ongoing InCommon Federation Manager issues

    We are continuing to experience issues with the InCommon Federation 
Manager. Technical staff are investigating, and we will provide updates as 
soon as more information is available. If you have questions in the meantime, 
please contact InCommon Support at 
.
    
    Thank you,
    
    David Shafer
    DevOps Manager,
    Internet2 Trust & Identity