Metadata backing store does not contain any EntityDescriptors with the ID

[Brent Putman]

On 7/29/16 3:57 PM, Eric Wedaa wrote:
>
> 2016-07-29 15:31:53,169 - DEBUG [org.opensaml.saml.metadata.resolver.impl.AbstractMetadataResolver:334] - Metadata backing store does not contain any EntityDescriptors with the ID: https://apps.collabservnext.com/sps/sp/saml/v2_0
>

That is indeed not necessarily an error.  You'll see that DEBUG on any
metadata provider which doesn't contain the requested entityID.


>
>
> and my metadata-providers.xml has this:
>
> <metadata:MetadataProvider id="VERSE" xsi:type="metadata:FilesystemMetadataProvider"
> metadataFile="/opt/shibboleth-idp/metadata/saml20SPCollabServ_IBM_SmartCloudNext_metadata.xml">
> </metadata:MetadataProvider>
>
> and THAT metadata file has this:
> <?xml version="1.0" encoding="UTF-8"?><md:EntityDescriptor xmlns:md="urn:oasis:names:tc:SAML:2.0:metadata" entityID="https://apps.collabservnext.com/sps/sp/saml/v2_0">
>

Is that the *only* metadata provider you have?  If so, that's a problem.

If not, then no, you'll see that DEBUG message on every metadata
provider in the  chain until it hits the one that contains the entityID
you're looking for.  E.g. if you have chain of providers A, B, and C in
that order and you have a resolution request for an entityID found only
in C, then you'll see that DEBUG message first coming out of A and B.


> Do I worry?  Is something on my side broken? It says "DEBUG so is this not really a problem?
>

Probably not, unless that's your only configured metadata provider. 
You have to look at that DEBUG message in context with the surrounding
log messages and also your configuration.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20160730/6f425eb7/attachment.html>