InCommon metadata support

[Tom Scavo <>]

On Tue, Sep 22, 2015 at 9:41 AM, David Gersic 
<>
 wrote:
>
> A suggestion for this page: how to detect fail(ing) metadata updates. A 
> simple paragraph on what to look for, how would I know if I'm affected by 
> this, that kind of thing. I think it's as simple as checking to see that 
> the file is updated and that the expiration date in the file is changing 
> appropriately.

I'll let Scott answer this, but yes, this is a good suggestion.

> It would also be helpful if, sometime between now and the 2016 import of 
> EduGAIN data, you could publish a test metadata URL so that IdP owners can 
> try it to see if it works before it goes live. I'm hoping that the EduGAIN 
> metadata will be first published to 
> (http://md.incommon.org/InCommon/InCommon-metadata-preview.xml) with an 
> announcement.

Yes, that's exactly the plan. We will let eduGAIN metadata bake in the
preview aggregate for one month. You should wire up your test IdP to
the preview aggregate now (or asap). Then you'll be ready to go.

Thanks David.

Tom

> ________________________________________
> From: 
> 
>  
> <>
>  on behalf of Tom Scavo 
> <>
> Sent: Tuesday, September 22, 2015 7:24 AM
> To: 
> 
> Subject: [InCommon NOTICE] How to Protect Against Failed Metadata Processes 
> [ACTION REQUIRED]
>
> You are receiving this message because you are a Site Administrator in
> the InCommon Federation or have otherwise subscribed to this mailing
> list. Your prompt action may be REQUIRED.
>
> Over the past few months, Shibboleth IdP deployers have reported
> numerous failed metadata processes. Evidence suggests that
> insufficient memory is the cause of these issues. In some cases, the
> root cause of the failure is not being logged.
>
> All Shibboleth IdP deployers in the InCommon Federation are strongly
> advised to take the following precautions to protect themselves
> against possible failed metadata processes:
>
> 1) Allocate at least 1024MB of heap space in the JVM
>
> 2) Enable DEBUG-level logging on the following Java classes:
> V2: org.opensaml.saml2.metadata.provider.AbstractReloadingMetadataProvider
> V3: 
> org.opensaml.saml.metadata.resolver.impl.AbstractReloadingMetadataResolver
>
> See this wiki page for details: https://spaces.internet2.edu/x/zgFwBQ
>
> Feel free to add a comment or suggestion to the above wiki page, or
> send a question to the metadata-support mailing list:
> https://lists.incommon.org/sympa/info/metadata-support
>
> ----
> InCommon Operations
>