Metadata backing store does not contain any EntityDescriptors with the ID

[Cantor, Scott]

On 7/29/16 3:57 PM, Eric Wedaa wrote:
> 
> Among other things, my third party SP who relies on unsolicited SSO fails.

You haven't indicated what "fails" means. What is the URL being used to
access the IdP?

>  I'm getting the following error in my idp-process.log file

That isn't an error.

If you're getting an error indicating it doesn't recognize the relying
party, which would lead to other log output then all I can say is
there's no metadata. You can post all the XML you like, and it won't be
true, so that means the files aren't what you think, where you think.
Wrong directory, wrong file, mistyped characeter somewhere, etc.

It usually ends up being obvious in hindsight, but people will post over
and over that it's 100% correct until the obvious mistake is identified,
just isn't obvious until then.

> But my relying-party.xml file has these lines in it
> .
> <metadata:MetadataProvider id="VERSE" xsi:type="metadata:FilesystemMetadataProvider"
> metadataFile="/opt/shibboleth-idp/metadata/saml20SPCollabServ_IBM_SmartCloudNext_metadata.xml">
> </metadata:MetadataProvider>

> and my metadata-providers.xml has this:

If you upgrade, I believe the script will copy relying-party.xml to
metadata-providers.xml, but the copy that is used to actually load the
metadata is metadata-providers.xml.

> Do I worry?  Is something on my side broken?

I have no idea, you haven't said what's wrong.

 It says "DEBUG so is this not really a problem?

Well, DEBUG is low level tracing information. It is not the sum total of
a trace nor does it indicate an error. If something's failing, there
would be something else in the log.

-- Scott