<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal>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.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>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:<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>ERROR Shibboleth.AttributeResolver.Query [1]: exception during
SAML query to <a
href="https://our.auth.service.url/idp/profile/SAML1/SOAP/AttributeQuery">https://our.auth.service.url/idp/profile/SAML1/SOAP/AttributeQuery</a>:
CURLSOAPTransport failed while contacting SOAP endpoint (<a
href="https://our.auth.service.url/idp/profile/SAML1/SOAP/AttributeQuery">https://our.auth.service.url/idp/profile/SAML1/SOAP/AttributeQuery</a>):
couldn't connect to host<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I’ve manually checked that the URL is accessible only
when using the proxy.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>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?<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>