SP entityID from multiple metadata sources

[Paul Engle]

This probably is not a good idea, but I can't seem to find a definite
answer in the docs. One of the vendors we use has submitted SP metadata
to InCommon for our instance. In my testing, it's come to light that we
need an additional AssertionConsumerService endpoint for the vanity URL
we plan to use. They've submitted the updated metadata to InCommon, and
in the fullness of time this would all resolve itself.

However, it was announced to the testers we'd be turning on SAML auth
*today* for this service, and I was trying to see if there's any way I
can make that happen. So my question is if it's at all feasible to set
up a MetadataProvider for just this SP that would have the necessary
update? Or will the same entityID appearing in two different MDProviders
just cause confusion and unpredictable behavior?

It's IdP version 2.3.8, if that makes a difference.

  -paul

-- 
Paul D. Engle              |  Rice University
Sr. Systems Administrator  |  Information Technology - MS119
(713)348-4702              |  PO Box 1892
pengle at rice.edu            |  Houston, TX 77252-1892