记录客户端登录续期集成状态
需求:将登录七天滑动续期来源提交纳入主分支集成记录。 实现:登记来源与合并提交、验证结果、发布约束及原主工作区脏文件阻塞。
This commit is contained in:
@@ -4,33 +4,35 @@ This file is the integrated default-branch snapshot. Feature tasks record progre
|
||||
|
||||
## Integrated Through
|
||||
|
||||
- {source task or merge commit}
|
||||
- `86ece3a`:客户端登录七天滑动续期来源提交。
|
||||
- `4dde8f32678baa81fd3ae3f6e7bd0d34b17885d6`:集成合并提交。
|
||||
|
||||
## Current Focus
|
||||
|
||||
The project is currently focused on {current focus}.
|
||||
客户端认证由 Electron Main 统一管理刷新凭据,并按真实用户活动维护七天闲置窗口。
|
||||
|
||||
## Recently Completed
|
||||
|
||||
- {YYYY-MM-DD}: {completed work summary}
|
||||
- 2026-08-07:集成客户端登录滑动续期、刷新令牌轮换持久化和终态清理保护。
|
||||
|
||||
## In Progress
|
||||
|
||||
- {in-progress item}
|
||||
- 协调认证服务端七天刷新令牌配置及共享 `app` OAuth 客户端发布。
|
||||
|
||||
## Next Recommended Steps
|
||||
|
||||
1. {next recommended step}
|
||||
2. {next recommended step}
|
||||
1. 确认所有共享 `app` 客户端支持原子保存轮换后的刷新令牌。
|
||||
2. 发布兼容客户端与认证服务后执行数据库迁移,并刷新 RegisteredClient Redis 缓存。
|
||||
|
||||
## Open Questions / Blockers
|
||||
|
||||
- {open question or blocker}
|
||||
- 存量刷新令牌不会被数据库迁移追溯缩短为七天。
|
||||
|
||||
## Risky Areas
|
||||
|
||||
- {risky area}
|
||||
- 刷新响应返回新令牌后、客户端安全落盘前的进程崩溃窗口会要求重新授权。
|
||||
- Linux 缺少受保护系统 keyring 时不会跨重启保存刷新凭据。
|
||||
|
||||
## Last Updated
|
||||
|
||||
{YYYY-MM-DD}
|
||||
2026-08-07
|
||||
|
||||
Reference in New Issue
Block a user