No profile handler...

[Klingenstein, Nate]

That would certainly be my first guess and something I would want to fix even if it were wrong.

You could always test the hypothesis by defining the, uh, space case.  You might get the literal space in the log files already, but I wouldn’t be shocked if that got piped through a trim somewhere or otherwise elided.


From: users [mailto:users-bounces at shibboleth.net] On Behalf Of IAM David Bantz
Sent: Wednesday, July 20, 2016 3:44 PM
To: users at shibboleth.net
Subject: No profile handler...

A recalcitrant service is sending this SAML request (captured in Firefox SAML tracer):

<samlp:AuthnRequest ID="_ceac0098-1829-4473-90e4-4be426650cb7"
                    Version="2.0"
                    IssueInstant="2016-07-20T20:32:27.878Z"
                    Destination="https://idp.alaska.edu/idp/profile/SAML2/Redirect/SSO "
                    ForceAuthn="false"
                    IsPassive="false"
                    ProtocolBinding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
                    AssertionConsumerServiceURL="https://adminuat.dc4.pageuppeople.com//gateway/SAML.aspx?binding=urn%3aoasis%3anames%3atc%3aSAML%3a2.0%3abindings%3aHTTP-POST<https://adminuat.dc4.pageuppeople.com/gateway/SAML.aspx?binding=urn%3aoasis%3anames%3atc%3aSAML%3a2.0%3abindings%3aHTTP-POST>"
                    xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol"
                    >
    <saml:Issuer xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion">https://adminuat.dc4.pageuppeople.com/</saml:Issuer>
    <samlp:NameIDPolicy AllowCreate="true" />
</samlp:AuthnRequest>

abd triggering this IdP response:
Error Message: No profile handler configured for request at path: /SAML2/Redirect/SSO
Is the trailing space after SSO potentially the culprit?
David Bantz
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20160720/35383d0c/attachment-0001.html>