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 SessionFixationProtectionStrategy creates a new HTTPSession based on an existing session, even if migrateSessionAttributes is enabled, it does not preserve the maxInactiveInterval value from the previous session.
The Javadoc doesn't say it does, so perhaps this isn't strictly a bug, but it seems like a reasonable expectation that SessionFixationProtectionStrategy would have this behavior.