BindingException with SAML2

Rafal Lalik rafal.lalik at
Wed May 31 12:05:36 EDT 2017

Well, I found the reason for my HTTP 500. It was not related to 
Shibboleth at all, it was false direction I was looking for solution.

For the record, the problem was with to short buffer for uwsgi, so the 
request was forwarded from properly working Shibboleth to uwsgi proxy, 
but uwsgi dropped it and it never reached django app.


W dniu 31.05.2017 o 17:40, Cantor, Scott pisze:
> On 5/31/17, 2:59 AM, "users on behalf of Rafal Lalik" <users-bounces at on behalf of rafal.lalik at> wrote:
>> I reviewed all my configuration and all looks good, I don't know what is the problem.
> The thread you found refers to a number of client-side considerations that apparently can cause a correctly issued response via POST to turn into a GET at the last minute and fail, but those have nothing to do with either the IdP or the SP. If that isn't the problem, then the IdP is apparently broken.
> Without a trace to see what kind of message it's sending to the SP, there's nothing else I can tell you about the cause. There's no simple mistake with the SP that could cause it. If the metadata in the IdP were fouled up such that the POST endpoint were associated with the artifact binding, I suppose that's a possible explanation, but this is all just speculation and there's no obvious reason that would happen.
> Basic SAML working knowledge is a general prereq to diagnosing these kinds of problems.
> -- Scott

Dr. Rafal Lalik

Technische Universität München
Fakultät für Physik, E62
James-Franck-Str. 1
85748 Garching

Room   :  2152
E-mail :  Rafal.Lalik at
Tel    :  (+49) 089 289 12488

More information about the users mailing list