Skip to Content.
Sympa Menu

metadata-support - Re: [Metadata-Support] significant slowdown in XML Signature validation

Subject: InCommon metadata support

List archive

Re: [Metadata-Support] significant slowdown in XML Signature validation

Chronological Thread 
  • From: Nick Roy <>
  • To: "" <>
  • Subject: Re: [Metadata-Support] significant slowdown in XML Signature validation
  • Date: Wed, 24 Feb 2016 19:32:23 +0000
  • Accept-language: en-US
  • Authentication-results:; dkim=none (message not signed) header.d=none;; dmarc=none action=none;
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:23

HEAnet, Ireland's NREN, has developed a very nice metadata management system,
called Jagger:

You may be interested in looking at this for local metadata management needs.


On 2/23/16, 9:05 AM,
on behalf of Tom Scavo"
on behalf of

>On Tue, Feb 23, 2016 at 10:42 AM, Jeffrey Eaton
> wrote:
>> On Feb 23, 2016, at 10:18 AM, Tom Scavo
>> <>
>> wrote:
>>> For the CMU SPs that interoperate with the CMU IdP only, would a
>>> single entity descriptor help? As an example, consider this metadata
>>> served from mdq-beta:
>>> If we provided a production version of the above metadata, would you
>>> find that useful?
>> That certainly would be preferable to consuming the full metadata file for
>> those SPs which only need one single IDP. I may still end up going down
>> the
>> path of having my own IDP metadata files signed and served locally, so that
>> I can have various combinations of files (ones with our test IDP, ones with
>> and which serves as our social
>> gateway, ones with our CS department's IDP which is not in InCommon, etc),
>> and then let the SP choose which they want to consume.
>Right, I get that, and btw, there has been discussion along these
>lines on the shib users mailing list recently:
>I predict that soon many campuses (and others) will be running their
>own metadata aggregation services.
>Hope this helps,

Archive powered by MHonArc 2.6.16.

Top of Page