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
Currently the ConcurrentSessionFilter only allows for a redirectUrl to be set and it always uses a RedirectStrategy. However we are using a JS front-end (still with a http session) and would like to be able to send a custom status code for this situation instead of a redirect.
The SessionManagementFilter uses an InvalidSessionStrategy with the default being a SimpleRedirectInvalidSessionStrategy. It would be nice and beneficial of the ConcurrentSessionFilter could use the same abstraction allowing for a more flexible handling of concurrent sessions for different front ends.
The text was updated successfully, but these errors were encountered:
rwinch
changed the title
Let the ConcurrentSessionFilter use the InvalidSessionStrategy
ConcurrentSessionFilter supports InvalidSessionStrategy
Sep 23, 2016
Currently the
ConcurrentSessionFilter
only allows for aredirectUrl
to be set and it always uses aRedirectStrategy
. However we are using a JS front-end (still with a http session) and would like to be able to send a custom status code for this situation instead of a redirect.The
SessionManagementFilter
uses anInvalidSessionStrategy
with the default being aSimpleRedirectInvalidSessionStrategy
. It would be nice and beneficial of theConcurrentSessionFilter
could use the same abstraction allowing for a more flexible handling of concurrent sessions for different front ends.The text was updated successfully, but these errors were encountered: