<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Oct 15, 2013 at 5:38 PM, Giovanni Bajo <span dir="ltr"><<a href="mailto:rasky@develer.com" target="_blank">rasky@develer.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
<br>
I'm working on deploying SAML in our infrastructure. As a first step, I deployed Shib as a SP for most services using Web Browser SSO, with mod_shib in Apache; that worked correctly. I am now working on configuring ECP for a few clients/services that require it.<br>
<br>
The clients that need to talk via ECP to the services are mostly written in Python; I've thus started prototyping ECP implementation using ecp.py (found here: <a href="https://wiki.shibboleth.net/confluence/display/SHIB2/ECP" target="_blank">https://wiki.shibboleth.net/confluence/display/SHIB2/ECP</a>).<br>
<br>
To make ecp.py work correctly to the end, I had to make two patches to its code; I would like to know whether they make sense or not:<br>
<br>
1) When POSTing to the IdP, I had to explicitly add a Content-Type header with value "text/xml" to the request, otherwise my IdP wouldn't recognize it as a SOAP/ECP request; by default, Python urllib sends Content-Type: application/x-www-form-urlencoded, which is surely wrong for a SOAP message.<br>
<br><span class="HOEnZb"><font color="#888888"><br></font></span></blockquote><div> </div><div>Thanks for catching that. I have modified the ecp.py Python demonstration client and updated it on the wiki.</div><div><br></div>
<div>Cheers,</div><div><br></div><div>Scott K</div></div></div></div>