InCommon Technical Discussions

["Domingues, Michael D" <>]

Hi Scott,

It appears that your setup is already downloading the InCommon metadata from the modern URL (md.incommon.org), so you should be good to go. Otherwise, you would have appeared in the list of sites still using the legacy URL (full list available at https://spaces.internet2.edu/x/5YVQBw).

InCommon retired the old URL back on February 14th. Because downloaded InCommon metadata has a two week validity window (from when it was produced), for sites that didn't update to the modern URL, the last version they downloaded would go stale / invalid on the 27th, causing all federated authentication to fail, which is what Nick was referring to.

Best,

Michael

---

From: <> on behalf of Green, Scott <>
Sent: Friday, February 23, 2018 10:09:15 AM
To:
Subject: [InC-Technical] MetaData Cutover ADFS 2.0 Question

 

I’m fairly new to the Identity Access with the InCommon setup here at EWU, and I recently learned of the metadata changes that InCommon Federation is making.  We are running ADFS 2.0 as our IDP and using the FEMMA tools to load the Relying Parties.  Can anyone tell me if this setup will be impacted by the MetaData changes that are scheduled to impact on the 27^th of this month? 

 

Thanks,

 

Scott W. Green Identity and Access Management Engineer    Office of Information Technology 113 Huston Hall    Cheney WA 99004 (509) 359-7268