Skip to Content.
Sympa Menu

metadata-support - Re: [Metadata-Support] Did something happen Friday, Sept 15 3-5pm?

Subject: InCommon metadata support

List archive

Re: [Metadata-Support] Did something happen Friday, Sept 15 3-5pm?

Chronological Thread 
  • From: "Hall, Gerry" <>
  • To: "" <>
  • Subject: Re: [Metadata-Support] Did something happen Friday, Sept 15 3-5pm?
  • Date: Thu, 21 Sep 2017 16:12:00 +0000
  • Accept-language: en-US
  • Authentication-results: spf=none (sender IP is ) ;
  • Ironport-phdr: 9a23:8zRprR01Fth6eBH/smDT+DRfVm0co7zxezQtwd8ZseMXLPad9pjvdHbS+e9qxAeQG96Ku7Qc06L/iOPJYSQ4+5GPsXQPItRndiQuroEopTEmG9OPEkbhLfTnPGQQFcVGU0J5rTngaRAGUMnxaEfPrXKs8DUcBgvwNRZvJuTyB4Xek9m72/q89pDXYAhEniaxba9vJxiqsAvdsdUbj5F/Iagr0BvJpXVIe+VSxWx2IF+Yggjx6MSt8pN96ipco/0u+dJOXqX8ZKQ4UKdXDC86PGAv5c3krgfMQA2S7XYBSGoWkx5IAw/Y7BHmW5r6ryX3uvZh1CScIMb7S60/Vza/4KdxUBLmiDkJOSMl8G/ZicJwgqBUrxygpxNjzIDbb5qYNOZlcaPYYd8WWXBMU8RXWidcAo28dYwPD+8ZMOpWrYfyvV8OrR+mCQKxBe3g1CVIhmX23KE0zu8sFg7G0xI6H9IUsHXYttX1O70WUeCx16TH0zDDb/RM2Tb98oTHbA0uoeyVUL92bMHfx04vFwbfgVWRr4zoJzKV1uIRvGic6upgUOWvi2g9pwF2uDivycEhgZTKiIIN0l3I6Dl1zYkvKdC3SkN3e9CpHZpKuyyaNoZ6Wt4uTmN0tCog17ELtoK3cDIXxJg7yBPTceGLfoaO7xn+TuieOy14i2hgeL+nhxa970ygyurkW8eszFtEqTZJnsfVun4QzxLf99GLSvxm8Ui/wzqP0B3T6v1fLkAziKrbLYMuzqQolpoJtkTDAjH5l1nqjK+XcUUk/PKk6+P6YrX6op+cMIh0igLkPqsyncy/BPw0MgkIX2eF5eSxzKDv8VH2TblQgfA7kLPVvZ7bKMgBpqO0AhdZ0oM55Ba+Czem3s4YnX4CLF9ddxKIkZLpO0vOIfziDfewmVCskDNwyv/YO73hBY/NL3jZnLj/YLl99lZQyBAvwtBH+5JUFrYBLeryWk/3qNPYCRo5Mwmzw+bhEtl90ZkeWW2WDq+cLqzSrUWH6f81LOmQfoAZoS39K+U95/72in85g0MdcLKt3ZsWc3C4Au9mL1uDbXrthNcBDXkFvhA4TOP0lF2OTyRfaGivUKIhtXkHD9fsCIrfT4yknLXExzqjBppMekhHDFuLFHLvccODQfhGIHaXL9NonjUYXP26Vpc50guynA78wL1iK+3SvCoCusSw+sJy4riZtRg28Xg8IMmHyXDHBzV7k3kSVnk21aR7iUF4zU2Sl6V0nqoLRpRo+/pVX1JiZtbnxOtgBoWqVw==
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:99

I experienced the same issue with several SP’s for which the source of
metadata is the InCommon aggregate file from about 3:28 PM until about 7:18
PM on this past Friday 15 September. Unfortunately, I was not made aware of
the issue until the next day Saturday by which the issue was resolved. I nor
anyone on my team made any changes nor did we take any corrective action.
Also, as the initial email indicates, the issue only affected SP’s for which
we rely on the InCommon aggregate file for as a source of metadata.

The IdP logs had erros like the following:|2017-09-15 03:27:27,382 - ERROR
[org.opensaml.saml.metadata.resolver.impl.HTTPMetadataResolver:313] -
Metadata Resolver FileBackedHTTPMetadataResolver InCommonMD: Error retrieving
metadata from
org.apache.http.conn.HttpHostConnectException: Connect to
[] failed: Connection refused|2017-09-15 03:27:27,382 - WARN
- Metadata Resolver FileBackedHTTPMetadataResolver InCommonMD: Problem
reading metadata from remote source; detected existing cached metadata,
skipping load of backup file

On 9/21/17, 11:47 AM,
on behalf of Cantor, Scott"
on behalf of

On 9/21/17, 8:42 AM,
on behalf of

on behalf of

> I ended up downloading a new InCommon metadata file and restarting our
> (since just restarting didn't change anything.) That was around 5pm and
> appeared to fix it. I was just wondering if I had actually fixed it,
or it
> was just a coincidence that it started working again.

As a matter of simple functional explanation, you cannot correct a
problem that may exist in your IdP's metadata by changing the metadata your
idP uses. Your IdP doesn't consume its own metadata.

If the problem was in an SP's metadata, then obviously reloading it and
changing the metadata the IdP uses is a very different matter.

What seems more likely is that your system broke in some way and
restarting it corrected that.

-- Scott


This e-mail message (including any attachments) is for the sole use of
the intended recipient(s) and may contain confidential and privileged
information. If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination, distribution
or copying of this message (including any attachments) is strictly

If you have received this message in error, please contact
the sender by reply e-mail message and destroy all copies of the
original message (including attachments).

Archive powered by MHonArc 2.6.19.

Top of Page