Transport option not being respected by MDQ metadata provider.
Krishna.Mohan at ucop.edu
Mon Nov 18 15:30:44 EST 2019
Thank you Scott. Appears to work when TransportOption elements is placed inside the root SPConfig element just before closing the SPConfig.
From: users <users-bounces at shibboleth.net> On Behalf Of Cantor, Scott
Sent: Saturday, November 16, 2019 7:26 PM
To: Shib Users <users at shibboleth.net>
Subject: Re: Transport option not being respected by MDQ metadata provider.
On 11/16/19, 6:25 AM, "users on behalf of Rod Widdowson" <users-bounces at shibboleth.net on behalf of rdw at steadingsoftware.com> wrote:
> The documentation  doesn't specify <TransportOptions> as a valid
> child for the DynamicMetadataProvider, just for the XML MetadataProvider and the code confirms this.
I believe that code uses the same HTTP code as the SOAP client, that's influenced by the top level TransportOption elements placed inside the root SPConfig element, but it's been a while and I wouldn't trust my memory other than to say it doesn't hurt anything to try it.
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
More information about the users