Using MetadataProvider behind web-proxy

[Simon Lundström]

Hey Tim!

When I setup an SP (in a container on a Kubernetes cluster, but
that's beside the point) that didn't have access to the Internet (except
via a proxy) I just used the HTTPS_PROXY and HTTP_PROXY environment
variables to point towards my proxy and everything just worked IIRC.

Also
NO_PROXY=127.0.0.0/8,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16,localhost,.svc,.cluster.local
might or might not be needed.

BR,
- Simon

On Mon, 2023-08-21 at 11:34:29 +0200, Tim van Dijen via users wrote:
> Hello all,
> 
> I'm using the MetadataProvider to pull in remote metadata XML's from behind a web-proxy.
> I was able to get this working by using <TransportOption provider="CURL" option="10004">myproxy.example.org:8080</TransportOption> inside the MetadataProvider-element, but with a couple of dozen providers this becomes a bit inept..
> According to the documentation it should be possible to set the <TransportOption> on the top-level, directly inside <SPConfig>, however if I do that the metadata cannot be pulled..
> 
> Is this a bug, or am I misinterpreting the docs? It would be really great if there is some way to configure this globally...
> Running the Shib SP @ v3.4.1
> 
> Kind regards,
> 
> Tim van Dijen

> -- 
> For Consortium Member technical support, see https://shibboleth.atlassian.net/wiki/x/ZYEpPw
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net