Question about TransportOption behavior

[Mark Scarbrough]

Hi all,

I have stumbled upon some unexpected behavior. We have an environment where a proxy is required to talk outbound HTTP. We added the TransportOption to the bottom of the shibboleth2.xml file just above the closing </SPConfig> tag. This works for the MDQ type MetadataProvider. However, when I define an XML type MetadataProvider with a URL source, I have found that it does not respect this TransportOption configuration. Instead, I must add the TransportOption element as a child of the specific MetadataProvider. Have others noticed this? Does the configuration need to be duplicated if there are multiple XML MetadataProviders?

Thanks,
-Mark
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20230911/a66a1552/attachment.htm>