admin-credential-bootstrap
Skill2 starsChanged 39 days agoMITView on GitHub
Web 项目初始管理员凭证发放规范:首启生成随机强密码、一次性打印到控制台并落盘 0600 密码文件、后续启动静默、用户改密后删除文件;禁止任何硬编码默认密码。
In this repository40 other files it gives its agents.
- ai-code-review-gateSkill
- ai-debt-ledgerSkill
- android-camera-devSkill
- android-device-debuggingSkill
- arch-dev-workflowSkill
- askills-syncSkill
- async-job-sse-upload-devSkill
- branching-workflowSkill
- disk-capacity-guardSkill
- edge-offline-pipeline-devSkill
- frontend-dev-workflowSkill
- github-ci-releaseSkill
- git-identitySkill
- installer-bundle-designSkill
- installer-preflightSkill
- installer-target-executionSkill
- mqtt-device-gateway-devSkill
- observability-designSkill
- ohos-media-devSkill
- onvif-rtsp-devSkill
- open-source-contributionSkill
- patent-applicationSkill
- patent-chartSkill
- patent-disclosureSkill
- patent-docketSkill
- patent-exam-policySkill
- patent-mapSkill
- patent-oaSkill
- patent-readerSkill
- patent-searchSkill
- project-brandingSkill
- redis-stream-rpcSkill
- robot-camerasSkill
- skill-distillationSkill
- skill-refreshSkill
- solution-racingSkill
- subagent-parallel-devSkill
- ui-responsive-listSkill
- user-facing-errorsSkill
- web-launch-dxSkill
The file
Files
初始管理员凭证发放(admin bootstrap)
核心原则:初始凭证是"一次性发放的密信",不是"写在 README 里的默认值"。硬编码默认密码(admin/123456、admin/admin)等于给所有部署实例留同一把钥匙。
1. 红线(禁止事项)
- 禁止硬编码初始/默认密码,禁止写进 README、示例配置、环境变量默认值。
- 禁止把初始密码写入持久化业务/审计日志(stdout 一次性提示可以)。
- 密码文件不进 git(.gitignore)、不进备份快照、不进监控采集目录。
2. 生命周期
状态判定以数据库中 admin 账号是否已初始化为准——密码文件只是提示载体,不是事实源:
| 阶段 | 行为 |
| 首次启动(DB 无 admin) | 生成随机强密码 → 入库 → 控制台打印提示块 → 写密码文件(0600) |
| 后续启动(DB 已有 admin) | 静默:不生成、不打印;密码文件即使仍在也不打印 |
| 用户修改密码成功 | 删除密码文件(存在才删);文件删除即凭证生命周期结束 |
| 重置密码(忘记密码入口) | 复用同一机制:新随机密码 → 打印 + 落盘 → 用户改掉后删文件 |
控制台提示块示例(面向部署者的运维通道,不是终端用户 UI):
====================================================
初始管理员已创建
账号:admin
密码:Xk9mP2xxxxxxxxxxxxxx
请立即登录并修改密码;修改后密码文件将自动删除
====================================================3. 实现要点
- 随机源必须密码学安全:Go 用
crypto/rand;禁止math/rand、时间戳、UUID 截取。长度 ≥16 字符,字母+数字+符号,剔除易混淆字符(0/O、1/l/I)。 - 生成时序:启动早期、初始化 admin 的同一路径内单次完成(与建账号同事务),避免并发双生成。
- 密码文件路径:放运行数据目录(如
data/initial-admin-password),容器部署时随卷持久化——换容器不丢;但后续启动的判定不依赖文件。 - 打印即一次性:stdout info 级单次输出;日志系统若把 stdout 全量落盘,需在该行加过滤标记或从持久日志侧排除。
- 删除时机:挂在"修改密码成功"的提交点之后(事务成功后 unlink,失败不删),删除失败记日志。
- 增强项(可选):首登强制改密;改完同样删文件。
- 与 user-facing-errors 衔接:登录失败走稳定错误码,不回显"初始密码文件存在性"之类的内部状态。
4. 检查清单
- 仓库与 README 全文搜不到默认密码字面量?
- 判定依据是 DB 而非文件——重启不打印、容器重建不误重新生成?
- 密码文件权限 0600、已进 .gitignore、随卷持久化?
- 改密成功即删文件,删失败有日志?
- 随机源 crypto/rand,长度 ≥16?
- 初始密码未进任何持久化日志/监控/备份?
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

