What info does an sp need to provide to an idp?

[Nate Klingenstein]

Christopher,

> Error Message: SAML 2 SSO profile is not configured for relying  
> party <our sp entity id>

This error means that the IdP doesn't recognize or trust the SP.   
Specifically, it doesn't know the SP's entityID.

> We're not sure how to proceed because it seems like a  
> misconfiguration on their end.  Does that sound correct?  What are  
> the general steps for registering an sp with an idp?

This depends on whether or not you're leveraging a federation to make  
the connection.  Later in this message, you imply this is bilateral,  
so...

> We've provided them with our sp's entity id and our certificate.   
> What other information do we need to provide to them?  What files do  
> they need to edit?

Assuming they're using an IdP that can consume metadata(and the logs  
look like Shibboleth logs), so it's easiest to just supply your  
metadata to them.  Otherwise, they will typically need an entityID,  
certificate, and an AssertionConsumerService URL.

> A part of the problem is that they've never registered an sp in the  
> system that isn't a part of InCommon.  Any tips?

They'll need to load your metadata by configuring their relying- 
party.xml with an appropriate MetadataProvider.

If you need to generate this metadata, you can do a pretty good  
approximation of it by accessing https://yoursite/Shibboleth.sso/Metadata 
.

Finally, if you need any attributes, then they need to configure  
attribute release in attribute-filter.xml.

This Wiki article may help, but mostly recapitulates in brief this  
email:

https://wiki.shibboleth.net/confluence/display/SHIB2/IdPSPCommunicate

Thanks,
Nate.