Add Explicit SessionAuthenticationStrategy Option
SessionAuthenticationFilter requires accessing the HttpSession to do its job. Previously, there was no way to just disable the SessionAuthenticationFilter despite the fact that SessionAuthenticationStrategy is invoked by the authentication filters directly. This commit adds an option to disable SessionManagmentFilter in favor of requiring explicit SessionAuthenticationStrategy invocation already performed by the authentication filters. Closes gh-11455
This commit is contained in:
@@ -2243,6 +2243,10 @@ Session-management related functionality is implemented by the addition of a `Se
|
||||
=== <session-management> Attributes
|
||||
|
||||
|
||||
[[nsa-session-management-authentication-strategy-explicit-invocation]]
|
||||
* **authentication-strategy-explicit-invocation**
|
||||
Setting this attribute to true will mean that `SessionManagementFilter` will not be injected and explicit invocation of SessionAuthenticationStrategy is required.
|
||||
|
||||
[[nsa-session-management-invalid-session-url]]
|
||||
* **invalid-session-url**
|
||||
Setting this attribute will inject the `SessionManagementFilter` with a `SimpleRedirectInvalidSessionStrategy` configured with the attribute value.
|
||||
|
||||
Reference in New Issue
Block a user