-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Logout fails due to invalidated session in WebFlux application #1523
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
Thanks for the detailed report @vpavic I have started looking into this, but haven't gotten as far as I'd like. Here are my notes thus far. What Changed?Dependency Management PluginIf I take the existing project and use the dependency management plugin instead of The difference in dependencies appears to be that for the What this suggests to me is that the change in dependency has changed how Spring Session is being used slightly. Redis MonitorUsing
Using the
Works SometimesI also have noticed that sometimes the sample project (as is) works while most of the time it fails. |
With Spring Boot As a sidenote, you can also use Gradle's native dependency resolution to enforce BOM's dependency versions by using |
I agree this should work despite the version of Netty. However, I wanted to note that this appears to be triggering the bug to happen. |
The situation remains unchanged with upgrade of sample project to Spring Boot
|
This is fixed via spring-projects/spring-security#7723 |
Is this definitely fixed? - I'm seeing this behaviour in Spring OAuth2.0 with a Redis session store.
The error I am seeing is similar to the original post
|
Having compiled the post above, I noticed the POST url is not the logout url - could this happen if a request was sent to the server from the browser with a session cookie that has already been invalidated very soon after the logout? |
@markhall82, if you're still having this issue I'd suggest to open a new issue describing the problem. Comments on closed issues tend to fall through the cracks quite easily. If you do open a new issue, please consider creating a minimal sample that can be used to reproduce this. Thanks! |
This appears to be a regression somewhere between Spring WebFlux, Spring Session and Spring Security.
The problem can be reproduced using
sample-websession
project from this repo (note: requires locally running Redis). Steps to reproduce:user
/password
This results in:
If Spring Boot is downgraded to
2.1.9.RELEASE
, everything works. It also works when upgraded to2.2.0.M4
, the trouble starts with2.2.0.M5
onwards.I've also tried working with
2.1.9.RELEASE
and upgrading Framework, Security and Session to current releases individually, but this also works.The text was updated successfully, but these errors were encountered: