Metadata precedence on entityID appearing twice in two different feeds.

[Tompkins,Charles R]

Hi All,

My IdP participates in the InCommon federation and our own, privately
registered federation by using both the InCommon metadata feed and our own
file-backed metadata stash for other SPs.

I have a situation where an entityID and metadata was registered in our
private federation with the same entityID as found in the InCommon feed, but
with different endpoints.

We are failing on the old "No return endpoint available for relying
party..." issue and I am thinking that it is picking the InCommon version of
the metadata's endpoints with which to qualify the authen request.

I've been reading
https://wiki.shibboleth.net/confluence/display/SHIB2/Metadata and its
children and haven't found how to negotiate metadata precedence for a given
entityID if that entityID appears twice (which makes me think my config is
unrational).  

In relying-party.xml, InCommon's metadata provider stanza appears first,
before the entityID-in-question's file-backed provider stanza.  Does this
matter?

Is it possible to override which metadata an IdP considers for a given
entityID if it appears in two places or is this just broken?

Thanks,

Charles Tompkins
UF Information Technology
Enterprise Infrastructure and Operations

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6020 bytes
Desc: not available
Url : http://shibboleth.net/pipermail/users/attachments/20141016/96a4ddfe/attachment-0001.bin