AWS + ECP?

[Brent Putman]

On 2/4/16 4:56 PM, Liam Hoekenga wrote:
>
> My bad.  I like pretty printing.  Here's the un-altered..
>
>

That looks good.  I even threw that into a file and OpenSAML ParserPool
can parse just fine.  So if that's literally the entirety of the request
body, it ought to work...

>  
> As downloaded, it does use the wrong content type.  I took a hint from
> John Dennis's message and added 
> -H "Content-Type: text/xml; charset=utf-8"
>
> The unmodified script does use application/x-www-form-urlencoded.  The
> SOAP request looks the same...

Ah, ok.  That makes more sense.


>
> The headers look the same, save the content-type...
> > POST /idp/profile/SAML2/SOAP/ECP HTTP/1.1
> > Host: shib-idp-test.www.umich.edu <http://shib-idp-test.www.umich.edu>
> > User-Agent: curl/7.46.0
> > Accept: */*
> > Authorization: Basic *************************
> > Content-Length: 735
> > Content-Type: application/x-www-form-urlencoded
>
> ...and both content types result in the IdP throwing a 500 (tho maybe
> for different reasons?)
>


Yeah, so with the right content type, does the IdP still log the same
XML parsing error?  If so, I'm at a loss.  Need to confirm, b/c it's
entirely possible that it's getting past the parsing but then throwing a
fatal error which results in the 500 and SOAP fault you previously
posted, for example something specific to the authN or ECP case.  For
example, not sure off-hand what that would return if for example basic
authN isn't configured correctly and so there's no REMOTE_USER visible
in the request.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20160204/0c2bf3e0/attachment.html>