Unable to decode incoming request

Cantor, Scott cantor.2 at osu.edu
Thu Mar 15 10:14:50 EDT 2018

> (My apologies,  I realize you're not being paid to answer emails) Could you tell
> me what in my original problem description led you to believe that was the
> problem?  I'm asking to try and learn from my mistakes.

The error in the email was a missing providerId parameter, which is a parameter we invented in the SAML 1.x era to support our proprietary request format, and that is backward-compatibly used in the SAML 2.0 Unsolicited request format. Neither of those endpoints is compatible with a SAML 2.0 request from an SP so it was obvious that the SP was manually told the wrong location to use.

All the endpoints we define for all the profiles are documented at https://wiki.shibboleth.net/confluence/display/IDP30/ProtocolsAndInterfaces

-- Scott

More information about the users mailing list