Adding a TrustingEngine for IDPv3
Benjamin Cherian
benjamin.cherian at villanova.edu
Fri Jan 30 12:35:25 EST 2015
That worked. Thanks!
On 1/30/15, 11:49 AM, "Rod Widdowson" <rdw at steadingsoftware.com> wrote:
>It looks from a skim of that link that the idea it to plug the trust
>engine
>into a MetadataProvider
>
>So what you need to do is to edit metadata-providers.xml and add in the
>metadata provider but rather than saying
>
><MetadataFilter xsi:type="SignatureValidation"
> xmlns="urn:mace:shibboleth:2.0:metadata"
> trustEngineRef="shibboleth.FedTrustEngine"
> requireSignedMetadata="true" />
>
>Just say
>
><MetadataFilter xsi:type="SignatureValidation"
> xmlns="urn:mace:shibboleth:2.0:metadata"
> certificateFile=" C:\Program
>Files\Internet2\Shib2Idp/credentials/adfssign.cer"
> requireSignedMetadata="true" />
>
>No trust engine needed.
>
>
>This is documented at
>https://wiki.shibboleth.net/confluence/display/IDP30/MetadataConfiguration
>but you'd need to know where to look.
>
>For the archive you'll usually not need to add a TrustEngine to
>metadata-providers.xml, but if you need to you can pop in into the
><MetadataFilter> (from 3.1 onwards).
>
>--
>To unsubscribe from this list send an email to
>users-unsubscribe at shibboleth.net
More information about the users
mailing list