AWS + ECP?

[Liam Hoekenga]

On Thu, Feb 4, 2016 at 4:05 PM, Brent Putman <putmanb at georgetown.edu> wrote:

> Hmmm, ok.  But does it also show the actual request body, or can you get
> curl to do that?  That's really what we want to know.  The IdP is saying
> that the request body isn't valid XML.


<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol">
    <S:Body>
        <samlp:AuthnRequest
xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol"
AssertionConsumerServiceURL="https://signin.aws.amazon.com/saml"
ID="_6946A4FA43404B198E4BC2AE432EC6B6" IssueInstant="2016-02-04T21:16:56"
ProtocolBinding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
Version="2.0">
            <saml:Issuer
xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion">urn:amazon:webservices</saml:Issuer>
            <samlp:NameIDPolicy AllowCreate="1"/>
            <samlp:Scoping>
                <samlp:IDPList>
                    <samlp:IDPEntry ProviderID="
https://shib-idp-test.www.umich.edu/idp/shibboleth"/>
                </samlp:IDPList>
            </samlp:Scoping>
        </samlp:AuthnRequest>
    </S:Body>
</S:Envelope>

I added the content-type header to the aws.plugin.bash that I referenced in
my initial message, along with "-v".
A bad password will return a 401, and a good one a 500 with a SOAP error:
<soap11:Envelope xmlns:soap11="http://schemas.xmlsoap.org/soap/envelope/">
    <soap11:Body>
        <soap11:Fault>
            <faultcode>soap11:Server</faultcode>
            <faultstring>An error occurred.</faultstring>
        </soap11:Fault>
    </soap11:Body>
</soap11:Envelope>

The ECP test scripts from the shib wiki work against our IdP

Liam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20160204/2f418c97/attachment-0001.html>