expressjs/session

Request: Option for refreshing the session ID

Open

#425 建立於 2017年2月9日

在 GitHub 查看
 (18 留言) (7 反應) (0 負責人)JavaScript (6,073 star) (977 fork)batch import
help wanted

描述

Sometimes, there is the need to refresh the session ID without loosing the session data.

Examples:

  1. Refreshing session ID after authentication (to protect against session fixation attacks) https://www.owasp.org/index.php/Session_fixation https://github.com/jaredhanson/passport/issues/192
  2. Manually refreshing session ID before it expires (e.g. if the user wants to keep working after the maximum session lifetime, but we do not want the same session ID to be used)

貢獻者指南

技術棧
nodejsexpressjavascript
領域
backendsecurity
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Basic understanding of Express sessionsKnowledge of session fixation attacks
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
55
研究方向
Review the express session source code, specifically the session regeneration logic. Examine the linked OWASP article and the referenced passport issue. Investigate the comments for any proposed implementations or rejected approaches. The goal is to add an option to regenerate the session ID while preserving session data, without breaking existing behavior.