I am using the reference from <a href="http://scm.iaasframework.com/hg/iaas-security/file/68ed40d91214/EcpProxy">http://scm.iaasframework.com/hg/iaas-security/file/68ed40d91214/EcpProxy</a>. My current work is just a prototype to get a basic understanding of the flow, what I really need is a library (ECP client and openSAML) for .Net, any recommendations?<br>
<br><div class="gmail_quote">On Mon, Jan 2, 2012 at 6:36 PM, Eric Dalquist <span dir="ltr">&lt;<a href="mailto:eric.dalquist@doit.wisc.edu">eric.dalquist@doit.wisc.edu</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">

  
    
  
  <div bgcolor="#FFFFFF" text="#000000">
    What are you using for an ECP client right now? Various uPortal
    associated portlets support ECP for delegated authentication. You
    can see source for the library that enables this here:<br>
<a href="https://source.jasig.org/sandbox/delegated-saml-authentication/trunk/" target="_blank">https://source.jasig.org/sandbox/delegated-saml-authentication/trunk/</a><br>
    <br>
    The idea is that the library provides a customized
    commons-httpclient 3.1 HttpClient class which sets the correct PAOS
    header and content type to notify the SP that ECP is supported by
    the client. If the SP provides the correct response the library
    handles the auth and the result is a HttpState which contains all
    the shib cookies and such. <br>
    <br>
    Another developer wrote the initial code but I&#39;ve done a lot of
    maintenance on the library since then.<br><font color="#888888">
    <br>
    -Eric</font><div class="im"><br>
    <br>
    On 1/2/12 5:55 PM, Anand Somani wrote:
    </div><div><div></div><div class="h5"><blockquote type="cite">But if I use the SSO browser profile, on auth failure
      I get redirected back to SP with a message that access was denied.
      <br>
      <br>
      I understand that with the container based approach it is not
      possible to do this, but why is it that Shibboleth (for ECP
      profile) uses the container auth (<a href="https://wiki.shibboleth.net/confluence/display/SHIB2/IdPAuthRemoteUser" target="_blank">https://wiki.shibboleth.net/confluence/display/SHIB2/IdPAuthRemoteUser</a>)
      and not the external auth (<a href="https://wiki.shibboleth.net/confluence/display/SHIB2/IdPAuthExternal" target="_blank">https://wiki.shibboleth.net/confluence/display/SHIB2/IdPAuthExternal</a>).
      It seems like with ExternalAuth it would be possible to return a
      SOAP error instead of 401.<br>
      <br>
      What would be the best thing to do, if I wanted to write a ECP
      Client then, I mean if things are not in the spec then it would
      almost depend on the IDP implementation which would force the
      client to be customizable and hence a headache to maintain?<br>
      <br>
      <br>
      <div class="gmail_quote">On Mon, Jan 2, 2012 at 3:15 PM, Chad La
        Joie <span dir="ltr">&lt;<a href="mailto:lajoie@shibboleth.net" target="_blank">lajoie@shibboleth.net</a>&gt;</span>
        wrote:<br>
        <blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
          In my opinion, and Scott may disagree, but because the SAML
          spec does<br>
          not actually cover authentication it also doesn&#39;t cover the
          case when<br>
          authentication is done by an external system and fails.<br>
          <br>
          In a perfect world, I would want the IdP to return a SAML
          error saying<br>
          authentication failed.  But there is no way to actually do
          that when you<br>
          call out to another system and it never returns control back
          to the IdP.<br>
          <div><br>
            On 1/2/12 6:08 PM, Anand Somani wrote:<br>
            &gt; So is response (for auth failure in case of ECP) within
            the spec or not?<br>
            &gt; The reason I ask is if our customer wants to use
            another Idp, would our<br>
            &gt; ECP code be different because it handles the credential
            validation<br>
            &gt; differently so instead of a 401, it returns a proper
            SOAP with auth denied.<br>
            &gt;<br>
            &gt; Thanks<br>
            &gt;<br>
            &gt;<br>
            &gt;<br>
            &gt; On Fri, Dec 30, 2011 at 3:56 PM, Chad La Joie &lt;<a href="mailto:lajoie@itumi.biz" target="_blank">lajoie@itumi.biz</a><br>
          </div>
          <div>&gt; &lt;mailto:<a href="mailto:lajoie@itumi.biz" target="_blank">lajoie@itumi.biz</a>&gt;&gt;
            wrote:<br>
            &gt;<br>
            &gt;     That is the expected behavior currently.
             Authentication occurs<br>
            &gt;     outside the IdP so its the web server or servlet
            container giving you<br>
            &gt;     that error.<br>
            &gt;<br>
            &gt;     On Fri, Dec 30, 2011 at 18:35, Anand Somani &lt;<a href="mailto:meatforums@gmail.com" target="_blank">meatforums@gmail.com</a><br>
          </div>
          <div>&gt;     &lt;mailto:<a href="mailto:meatforums@gmail.com" target="_blank">meatforums@gmail.com</a>&gt;&gt;
            wrote:<br>
            &gt;     &gt; Follow up question on the setup for ECP.
            Everything seems to work as<br>
            &gt;     &gt; expected for a successful login, but for a bad
            password the client<br>
            &gt;     gets a<br>
            &gt;     &gt; 401 and a html response body, I would have
            expected a SOAP<br>
            &gt;     response/fault<br>
            &gt;     &gt; (from Idp) with a rejection/denied that I
            could pass to SP. Is<br>
            &gt;     this not the<br>
            &gt;     &gt; correct expectation? Maybe my Idp setup is not
            complete, even<br>
            &gt;     though it<br>
            &gt;     &gt; seems to work?<br>
            &gt;     &gt;<br>
            &gt;     &gt; Thanks<br>
            &gt;     &gt;<br>
            &gt;     &gt;<br>
            &gt;     &gt; On Wed, Dec 21, 2011 at 5:56 PM, Cantor, Scott
            &lt;<a href="mailto:cantor.2@osu.edu" target="_blank">cantor.2@osu.edu</a><br>
          </div>
          <div>&gt;     &lt;mailto:<a href="mailto:cantor.2@osu.edu" target="_blank">cantor.2@osu.edu</a>&gt;&gt;
            wrote:<br>
            &gt;     &gt;&gt;<br>
            &gt;     &gt;&gt; For the sake of the list archive, the
            crash was in an old<br>
            &gt;     log4shib version<br>
            &gt;     &gt;&gt; that was fixed several years ago and has
            nothing to do with ECP in<br>
            &gt;     &gt;&gt; particular.<br>
            &gt;     &gt;&gt;<br>
            &gt;     &gt;&gt; -- Scott<br>
            &gt;     &gt;&gt;<br>
            &gt;     &gt;&gt; --<br>
            &gt;     &gt;&gt; To unsubscribe from this list send an
            email to<br>
            &gt;     &gt;&gt; <a href="mailto:users-unsubscribe@shibboleth.net" target="_blank">users-unsubscribe@shibboleth.net</a><br>
          </div>
          &gt;     &lt;mailto:<a href="mailto:users-unsubscribe@shibboleth.net" target="_blank">users-unsubscribe@shibboleth.net</a>&gt;<br>
          <div>&gt;     &gt;<br>
            &gt;     &gt;<br>
            &gt;     &gt;<br>
            &gt;     &gt; --<br>
            &gt;     &gt; To unsubscribe from this list send an email to<br>
            &gt;     &gt; <a href="mailto:users-unsubscribe@shibboleth.net" target="_blank">users-unsubscribe@shibboleth.net</a><br>
          </div>
          &gt;     &lt;mailto:<a href="mailto:users-unsubscribe@shibboleth.net" target="_blank">users-unsubscribe@shibboleth.net</a>&gt;<br>
          &gt;<br>
          &gt;<br>
          &gt;<br>
          &gt;     --<br>
          &gt;     Chad La Joie<br>
          &gt;     <a href="http://www.itumi.biz" target="_blank">www.itumi.biz</a>
          &lt;<a href="http://www.itumi.biz" target="_blank">http://www.itumi.biz</a>&gt;<br>
          <div>&gt;     trusted identities, delivered<br>
            &gt;     --<br>
            &gt;     To unsubscribe from this list send an email to<br>
            &gt;     <a href="mailto:users-unsubscribe@shibboleth.net" target="_blank">users-unsubscribe@shibboleth.net</a><br>
          </div>
          &gt;     &lt;mailto:<a href="mailto:users-unsubscribe@shibboleth.net" target="_blank">users-unsubscribe@shibboleth.net</a>&gt;<br>
          <div>
            <div>&gt;<br>
              &gt;<br>
              &gt;<br>
              &gt;<br>
              &gt; --<br>
              &gt; To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net" target="_blank">users-unsubscribe@shibboleth.net</a><br>
              --<br>
              To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net" target="_blank">users-unsubscribe@shibboleth.net</a><br>
            </div>
          </div>
        </blockquote>
      </div>
      <br>
      <br>
      <fieldset></fieldset>
      <br>
      <pre>--
To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net" target="_blank">users-unsubscribe@shibboleth.net</a>
</pre>
    </blockquote>
  </div></div></div>

<br>--<br>
To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net">users-unsubscribe@shibboleth.net</a><br></blockquote></div><br>