-
Notifications
You must be signed in to change notification settings - Fork 131
Unsupported binding HTTP-POST with MDQ #410
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Looks like I was looking at the wrong place.
|
So you are getting errors from too long request URI ... that looks like related to IdentityPython/pysaml2#819 - where the AuthnRequest has a large XML signature embedded (designed for use with HTTP-POST), but it is sent via HTTP-Redirect (where a detached signature should be used instead). Could it be mixed up HTTP-POST and HTTP-Redirect endpoints/bindings? Cheers, |
I checked again and the metadata for the IDP specifies REDIRECT. Seems like updating NGINX broke some other services for us as well, since they lowered the max size... |
Hi, I'm looking at this now. I see ARNES has in eduGAIN both an SP ( What is the sequence of steps to reproduce this in a browser? Where should I start / what to select? Cheers, |
It's the IdP that I was transferring to. |
@craftbyte - but what sequence of steps would replicate this issue? If I just pick "an SP in eduGAIN" (like the SWITCH Attribute Viewer)and try logging in with ARNES, I get to this IdP ... but where does the double-signed message come into play? That would be after successful authentication at the IdP - which I'd not have access to? |
I am trying to set up a new SATOSA instance to do eduGAIN SP to local SP federation (use edugain to log into local keycloak). When setting it up, after getting past the discovery service, I get a 500 error and logs relating to Unsupported binding for HTTP-POST. Can anyone help here?
I am running pyFF in an adjacent container.
Here is the backend config:
Code Version
Docker 8.1.1
Expected Behavior
Redirect to IdP works
Current Behavior
The text was updated successfully, but these errors were encountered: