technical-discuss - [InC-Technical] InCommon MDQ metadata update schedule: 5pm ET
Subject: InCommon Technical Discussions
List archive
- From: "Basney, Jim" <>
- To: "" <>
- Subject: [InC-Technical] InCommon MDQ metadata update schedule: 5pm ET
- Date: Wed, 23 Oct 2019 14:48:32 +0000
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=illinois.edu; dmarc=pass action=none header.from=illinois.edu; dkim=pass header.d=illinois.edu; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=LMC+Lncr+9bbZkEXYdonzlvv1SSfpUf6yKiEGCyvmQo=; b=j0MkLl7UWh4uJ8v0Q3D6303DIczRIAe7Y5IP7zG+LSRb3R6tA/Kmb/ih5z2pn6ajm3ozAJrs0lwGQ18Ry1Oi7vaEf+i681jHaE0PfJr5B8YOzEItkCabBUFLpTPEa0nAQiR1S9NEKGjkinxmc7f5JOI5qTMC5MeTclaiLXcjQiTC/JPpiy/JBN8Lo2F4NW+uCcpJSxzhkL56JZlKCZgbc+JznHi44LNqMHa39o244dUPr3u66hz1e9Hor9a1D61GrCtqCKQjpYRWqHsqh5tgslo3LJDOGc1BCxpzjvPt9HLgHwahJePmYvxwSaMiY8uSYbO33KK1AZ/RPZ5eplrNoA==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=h0QhXRbvo558hPK9LjoSb2X5ZTV9t+TDwRcMDBY362tq3tf4z0S+zPsZiW47PL0Zt1wy7HPo2+8D67kLG3Jaem9tZC14DFBuKCDIyW9Y6D+VnG4V0U3Qg/117zgx5CJsLp6zqxlPTqfbiCvIIYopbxAReW4gAQPOVSSIuxI8Rc2/PjhguKA9PtiMBmr9/Y3T/k3l1mVQVcpnCwvpYzkxWE5nkznJcrctaSu8MwO73iN4I0zqG73n/EzeS6CLObSF7etHlIRDuupeEK5ooCRPQscHP5Kv33Wj5sNwjr4onh4xUvxEUT21A7JeHxurox/JXaBF2BUVUxEUNAUzaljUKA==
Hi,
If I understand correctly, metadata published by mdq.incommon.org is updated
each business day at 5pm ET. If true, I request InCommon to reconsider this
schedule.
For comparison, I see updates from
http://md.incommon.org/InCommon/InCommon-metadata.xml each business day
around 3pm ET, which gives us a few hours left in the workday to identify any
problems caused by the metadata update and contact for
assistance when needed. By contrast, since switching to mdq.incommon.org,
problems with the metadata appear late in the evening, and we don't hear back
from until the next business day.
For example, on Fri Oct 18 around 5pm ET https://idp.fnal.gov/idp/shibboleth
was removed from InCommon metadata, causing problems for Fermilab users
trying to log on to CILogon over the weekend. Since was
unable to assist until Monday morning, we configured a manual metadata update
on the CILogon servers to continue providing service over the weekend. On
Monday morning, InCommon acted quickly to add
https://idp.fnal.gov/idp/shibboleth back in to
http://md.incommon.org/InCommon/InCommon-metadata.xml at 9:26 ET, but since
CILogon now uses mdq.incommon.org, we didn't see the update until 5pm ET on
Monday. It took me a while on Monday afternoon to figure out why the CILogon
servers weren't seeing the metadata update after told us
the problem was resolved.
My expectation was that the move to MDQ would deliver more up-to-date
metadata, not less.
Sincerely,
Jim
- [InC-Technical] InCommon MDQ metadata update schedule: 5pm ET, Basney, Jim, 10/23/2019
- <Possible follow-up(s)>
- Re: [InC-Technical] InCommon MDQ metadata update schedule: 5pm ET, Albert Wu, 10/23/2019
Archive powered by MHonArc 2.6.19.