-
Notifications
You must be signed in to change notification settings - Fork 433
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
Logout response validation failed with Authentication failed error #489
Comments
@alexanderzobnin, is it because of this that the trivial example |
@rgl not sure, error here is happening during logout response processing, so it should not end up with 404, but with error ("Authentication failed"). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When single logout is enabled, SP fails to perform logout with error
Authentication failed
. I tried to debug and found that error is happening inValidateLogoutResponseRedirect()
. It returns errors likeinvalid character entity &d (no semicolon)
orinvalid UTF-8
. After some investigation, I've found that it's related to compressed response. Error happens here:saml/service_provider.go
Line 1538 in 2aeb2ef
rawResponseBuf
contains compressed bytes and should be deflate first. In previous versions it was correct:saml/service_provider.go
Line 1561 in 5e0ffd2
where
gr
is deflated string:saml/service_provider.go
Line 1538 in 5e0ffd2
So I think the fix is pretty straightforward.
The text was updated successfully, but these errors were encountered: