Shibboleth SP 3; MetadataProvider via proxy

[Marcello Marangio]

Hi
yes I already did that:

<MetadataProvider type="Chaining">
                        <TransportOption provider="CURL" option="10004">proxy.in.cloud.innova.puglia.it:3128</TransportOption>
     <MetadataProvider type="XML" url="https://login.regione.puglia.it/identity/metadata/saml2" backingFilePath="/etc/shibboleth/idp/login.regione.puglia.it.xml" reloadInterval="180000" > </MetadataProvider>
                             </MetadataProvider>

but what i get is

2022-06-23 16:10:09 ERROR OpenSAML.MetadataProvider.Chaining : MetadataProvider child element of type TransportOption ignored


any clue?
M
> 
> Message: 1
> Date: Thu, 23 Jun 2022 16:33:40 +0200
> From: Marcello Marangio <m.marangio at innova.puglia.it>
> To: Shib Users <users at shibboleth.net>
> Subject: Shibboleth SP 3; MetadataProvider via proxy 
> Message-ID: <A211C68B-00E6-495D-ABB8-C0AA15CAFBDA at innova.puglia.it>
> Content-Type: text/plain;	charset=us-ascii
> 
> Hi all
> is it possible to configure a proxy directive in the metadataprovider tag in shibboleth2.xml?
> thanks
> Marcello
> 
> 
> 
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Thu, 23 Jun 2022 15:46:39 +0100
> From: "Rod Widdowson" <rdw at steadingsoftware.com>
> To: "'Shib Users'" <users at shibboleth.net>
> Subject: RE: Shibboleth SP 3; MetadataProvider via proxy 
> Message-ID: <01ac01d88710$0c3499f0$249dcdd0$@steadingsoftware.com>
> Content-Type: text/plain;	charset="us-ascii"
> 
>> is it possible to configure a proxy directive in the metadataprovider tag in shibboleth2.xml?
> 
> Yes, you want the TransportOption there is an example here [1]
> 
> https://shibboleth.atlassian.net/wiki/spaces/SP3/pages/2065335485/CURLTransport
> 
> 
> 
> ------------------------------
> 
> Subject: Digest Footer
> 
> -- 
> 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
> 
> 
> ------------------------------
> 
> End of users Digest, Vol 132, Issue 19
> **************************************