AW: IDP3.2.1 Unable to decode incoming request

[Käfer Thomas]

Dear Peter,

thanks for your reply!


Well, from as far as I unsterstand what the debug browser tools show me, yes the browsers send POST requests.


It exhibits the same behavior for any configured SP, including your own sp.eduid.at.

You can easily test this yourself without having a valid username/password combination. If it works as it should, you should stay at the login form and simply get an error that the combination is wrong. If you see the error you get to the stale request page instead.


Kind Regards,

Thomas K.



________________________________
Von: users <users-bounces at shibboleth.net> im Auftrag von Peter Schober <peter.schober at univie.ac.at>
Gesendet: Dienstag, 12. Juli 2016 13:38
An: users at shibboleth.net
Betreff: Re: IDP3.2.1 Unable to decode incoming request

* Käfer Thomas <thomas.kaefer at fh-campuswien.ac.at> [2016-07-12 13:33]:
> 2016-07-12 12:14:20,908 - ERROR
> [org.opensaml.profile.action.impl.DecodeMessage:73] - Profile Action
> DecodeMessage: Unable to decode incoming request
> org.opensaml.messaging.decoder.MessageDecodingException: This
> message decoder only supports the HTTP POST method

You're sure the SP causes your browser to sent an HTTP POST request
there, not HTTP GET? Is that a public SP I can test myself?
(Of course that doesn't explain other browsers working, just something
to get out of the way.)
-peter
--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20160712/dd6b73bc/attachment.html>