Using proxy server for AttributeResolver.Query

Clubok, Ken Ken.Clubok at osumc.edu
Fri Aug 26 21:24:11 BST 2011


My web server is on a box that apparently can do very little without going through a proxy server.  Thanks to information on this list, I learned how to use a <TransportOption> tag inside the <MetadataProvider> configuration, so that we can access the metadata provider through the proxy.

This is great for authentication, but we run into the same problem again when we try to get attributes.  The shibd_warn.log file reads thus:

ERROR Shibboleth.AttributeResolver.Query [1]: exception during SAML query to https://our.auth.service.url/idp/profile/SAML1/SOAP/AttributeQuery: CURLSOAPTransport failed while contacting SOAP endpoint (https://our.auth.service.url/idp/profile/SAML1/SOAP/AttributeQuery): couldn't connect to host

I've manually checked that the URL is accessible only when using the proxy.

I assume that the solution is to place another <TransportOption> tag somewhere in the configuration.  But I don't know where it goes.  I have tried putting it within the root <SPConfig> element, but then the Shibboleth service simply refuses to start.  Any ideas?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20110826/160b6164/attachment.html 


More information about the users mailing list