[SHIRO-170] Force New Session ID on Authentication

• Type: New Feature
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 1.0.0, 1.1.0, 1.2.0
• Fix Version/s: 2.0.0
• Component/s: Authentication (log-in), Configuration
• Assignee: Unassigned
• Reporter: Jakob Külzer
• Created: 24/May/10 20:34
• Updated: 06/Mar/23 08:06

Description

I am working on an application that has very high security standards. One of the issues raised after a full audit of the app is that it might be vulnerable for session fixation attacks. Shiro does not reset the Session ID after successful authentication, which would prevent this type of attack.

IMHO this would add another level of security to Shiro beneficial for all kinds of applications.

OWASP has a good page on session fixation attacks: http://www.owasp.org/index.php/Session_fixation