'relying party' error

[David Bantz]

I’m integrating my IdP with a vendor’s Shibboleth SP.  I’m puzzled by the error he reports is triggered after receiving my IdP’s SAML:

> I am seeing the following error when redirected:
> 
> Error Message: SAML 2 SSO profile is not configured for relying party https://uaacommons2.wpengine.com
> The entity ID we are using in apache is urn:mace:uncommon:alaska.edu. Is this correct for your test? Please advise. Thank you.
> 

1) The entity in the Error Message is the vendor’s entityID as per the metadata provided me.
What would trigger the SP to request relying party configuration for itself?

2) the entityID of my IdP is  urn:mace:incommon:alaska.edu but apart from the amusing typo,
why would Apache on the service side need my IdP’s entityID?

3) The first attempt of the vendor to provide their SP metadata at http://vendor-server/Shibboleth.sso/Metadata
mysteriously had the entityID of my IdP.    That particular problem has been corrected by the vendor at my insistence, 
but I wonder if there could be some systematic confusion of IdP and SP on their part.

David Bantz
UAlaska
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20140826/7ce6be59/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: Message signed with OpenPGP using GPGMail
Url : http://shibboleth.net/pipermail/users/attachments/20140826/7ce6be59/attachment-0001.bin