<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<div class="moz-cite-prefix">On 9/11/19 6:04 PM, Brent Putman wrote:<br>
</div>
<blockquote type="cite"
cite="mid:d86ad4c4-607b-895e-3ef2-c20522e16e92@georgetown.edu">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p><br>
</p>
<div class="moz-cite-prefix">On 9/11/19 1:42 PM, Cantor, Scott
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:F78A2D28-C81E-4603-AE9C-350A4BC8A6DF@osu.edu">
<pre class="moz-quote-pre" wrap="">On 9/11/19, 1:37 PM, "users on behalf of Bickel, David" <a class="moz-txt-link-rfc2396E" href="mailto:users-bounces@shibboleth.netonbehalfofjdbickel@iu.edu" moz-do-not-send="true"><users-bounces@shibboleth.net on behalf of jdbickel@iu.edu></a> wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap=""> I did have to setup traffic to get InCommon metadata using proxyHost & proxyPort. I am not seeing a way to do
something similar for the Duo NonBrowser configuration. Am I missing something obvious in the documentation?
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap=""><a class="moz-txt-link-freetext" href="https://wiki.shibboleth.net/confluence/display/IDP30/DuoAuthnConfiguration#DuoAuthnConfiguration-AdvancedHttpClientScenarios" moz-do-not-send="true">https://wiki.shibboleth.net/confluence/display/IDP30/DuoAuthnConfiguration#DuoAuthnConfiguration-AdvancedHttpClientScenarios</a>
</pre>
</blockquote>
<p><br>
</p>
<p>Yep, the base HttpClient builder supports various proxy
properties. Those same properties are what gets used by the
metadata providers via the custom XML schema and parsers.</p>
<br>
</blockquote>
<p><br>
</p>
<p>FYI, I also added this info and example to the Duo wiki page
above.</p>
</body>
</html>