Why to configure SP generated metadata in SP and IDP?
<p>I'm using the spring saml example application spring-security-saml2-sample. Here I discovered two parts with generated metadata: </p>

<ol>
<li>I've <a href="http://docs.spring.io/spring-security-saml/docs/1.0.x/reference/html/chapter-quick-start.html#quick-start-sp-metadata-to-idp" rel="nofollow">generated sp metadata</a> via the <a href="http://localhost:8080/spring-security-saml2-sample/saml/web/metadata" rel="nofollow">admin interface</a> and uploaded the metadata to the IDP (<a href="https://idp.ssocircle.com/sso/hos/ManageSPMetadata.jsp" rel="nofollow">ssocircle</a>).</li>
<li>Further a <a href="http://docs.spring.io/spring-security-saml/docs/1.0.x/reference/html/configuration-metadata.html#configuration-metadata-sp-generation" rel="nofollow">MetadataGenerator</a> must be configured or <a href="http://docs.spring.io/spring-security-saml/docs/1.0.x/reference/html/configuration-metadata.html#configuration-metadata-sp-import" rel="nofollow">preconfigured metadata</a> must be defined in the spring application (SP).</li>
</ol>

<p>So why do I need SP generated metadata twice?
If MetadataGenerator is configured, I've even a static version (uploaded to IDP) and a dynamic local version.</p>