SEC-2470: SessionFixationProtectionStrategy should migrate maxInactiveInterval #2693
Labels
in: web
An issue in web modules (web, webmvc)
type: breaks-passivity
A change that breaks passivity with the previous release
Milestone
Dan Dormont (Migrated from SEC-2470) said:
When
SessionFixationProtectionStrategy
creates a newHTTPSession
based on an existing session, even ifmigrateSessionAttributes
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.The text was updated successfully, but these errors were encountered: