Technolutions incident

Metadata missing from InCommon MDQ service

Notice Resolved View vendor source →

Technolutions experienced a notice incident on October 7, 2021 affecting Slate, lasting 1d 6h. The incident has been resolved; the full update timeline is below.

Started
Oct 07, 2021, 03:24 PM UTC
Resolved
Oct 08, 2021, 10:07 PM UTC
Duration
1d 6h
Detected by Pingoru
Oct 07, 2021, 03:24 PM UTC

Affected components

Slate

Update timeline

  1. identified Oct 07, 2021, 03:24 PM UTC

    We have been notified by several organizations that the InCommon MDQ service is not returning the metadata for the Slate entity ID this morning. While this is an issue with the InCommon MDQ service, not with Slate, it may prevent some organizations from logging into Slate with their single sign-on if they are accessing the Slate metadata from the InCommon MDQ service or if Slate is accessing their metadata from the InCommon MDQ service and the metadata is missing. InCommon is aware of the issue, has alerted their subscribers, and is working towards a resolution. In the meantime, organizations can either consume the InCommon metadata aggregate, which correctly contains the Slate metadata, or load the Slate metadata directly from https://slate.technolutions.net/manage/service/saml. Organizations that are using other means of single sign-on or that are consuming the Slate metadata directly or their Slate instance metadata directly are unaffected.

  2. identified Oct 07, 2021, 08:50 PM UTC

    InCommon continues to work towards a resolution. Slate services remain online and operational, and this is an issue affecting the availability of certain metadata through the InCommon MDQ service. InCommon is posting regular status updates here: https://spaces.at.internet2.edu/display/federationops/2021-10-07+MDQ+intermittent+outage There will be no further updates to this post until there is a substantive resolution to the InCommon issue. For incremental updates, we recommend following the InCommon status page linked above.

  3. resolved Oct 08, 2021, 10:07 PM UTC

    InCommon has updated their status page to reflect that the issue has now been resolved.