You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When protecting a Webflux route with oauth2login(), the redirect back to that route after login misses any query parameters passed in the original request to that route. That seems to be caused by WebSessionServerRequestCache only saving the path, not the parameters.
For the purposes of the following sections, let's say the client requests GET /protected?foo=bar, but is not logged in yet.
Actual Behavior
After the OAuth2 login flow succeeded, the client gets redirected to /protected (note the missing ?foo=bar).
Expected Behavior
The query parameters are retained. The redirect after login would go to /protected?foo=bar.
Details
It seems as if WebSessionServerRequestCache only saves the request path. It should save URL query parameters in addition.
The text was updated successfully, but these errors were encountered:
Previously, URL query parameters were lost when saving a request
in WebSessionServerRequestCache. Now it is properly saved and
restored.
Fixes: gh-6421
Previously, URL query parameters were lost when saving a request
in WebSessionServerRequestCache. Now it is properly saved and
restored.
Fixes: gh-6421
Summary
When protecting a Webflux route with
oauth2login()
, the redirect back to that route after login misses any query parameters passed in the original request to that route. That seems to be caused byWebSessionServerRequestCache
only saving the path, not the parameters.For the purposes of the following sections, let's say the client requests
GET /protected?foo=bar
, but is not logged in yet.Actual Behavior
After the OAuth2 login flow succeeded, the client gets redirected to
/protected
(note the missing?foo=bar
).Expected Behavior
The query parameters are retained. The redirect after login would go to
/protected?foo=bar
.Details
It seems as if
WebSessionServerRequestCache
only saves the request path. It should save URL query parameters in addition.The text was updated successfully, but these errors were encountered: