Using custom metadata for my SP

Peter Schober peter.schober at
Thu Feb 6 12:49:25 EST 2020

* Vjger <vjger69 at> [2020-02-06 18:29]:
> > You still haven't explained why you think the metadata must be
> > different for different consumers of that metadata.
> > I'd try to avoid such a situation if at all possible.
> It's not. 
> Simply, I started with a standard configuration Sp-Idp both Shibboleth
> (changing only entityId) and all worked fine. In other words I used the
> metadata obtained by Shibboleth.sso/Metadata because I had not other
> particular requirements. We can say this was the first milestone.
> The second milestone is the integration with governments idps and studing
> the documentation for the validation of the SP metadata I found that more
> SAML informations (compared to standard metadata) are required. My goal is
> now to write a (new) custom metadata good as for the internal IDP as for
> federated IDPS.

"More information is required" is not the same thing as
"Different IDPs have mutually exclusive requirements on my SP's metadata".

If more data is needed then add more data.
That still doesn't make the metadata specific to any one IDP.

But whatever, you got your question answered that you may edit (and
transmit) a plain text file as desired.


More information about the users mailing list