AWS + ECP?
Liam Hoekenga
liamr at umich.edu
Thu Feb 4 15:58:51 EST 2016
On Thu, Feb 4, 2016 at 3:53 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:
> We probably figured this out months ago, the problem is just the script
> and use of curl, it defaults the Content Type to form-encoded if you don't
> set it.
The content-type on my POST seems to be text/xml:
> POST /idp/profile/SAML2/SOAP/ECP HTTP/1.1
> Host: shib-idp-test.www.umich.edu
> Authorization: Basic BLAHBLAHBLAHSTUFF
> User-Agent: curl/7.46.0
> Accept: */*
> Content-Type: text/xml; charset=utf-8
> Content-Length: 735
The 500 returned by the IdP is also text/xml
I think a big part of the AWS issue is our virtualization guys don't know
anything about SAML and our SAML guys (incl me) don't know a damn thing
about AWS.
I pointed the virt guy at some command line AWS stuff that uses form based
auth, and I /think/ that works.
> I can speculate your AWS issue might be that, but you'd have to sniff it.
I could do that if necessary. What are you thinking?
Liam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20160204/07fe079e/attachment.html>
More information about the users
mailing list