opensabre / opensabre/base-sysadmin
feat: 内部 Token 密钥仓库支持 Nacos 鉴权
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1
- Forks
- 3
- Avg merge
- 4h 24m
- Merged PRs (30d)
- 11
Description
问题
内部 Token 密钥控制面访问 Nacos 时尚未支持用户名/密码或访问 Token 等鉴权配置，启用 Nacos 安全后无法可靠读写密钥。
工作项
- 支持 Nacos 认证所需配置并避免敏感信息泄露
- 复用项目统一 Nacos 客户端配置与凭证来源
- 覆盖认证失败、凭证更新、超时和重试场景
- 补充安全部署文档
验收标准
- 开启 Nacos 鉴权的环境可完成密钥创建、读取和轮换
- 日志与接口响应不暴露凭证
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the internal Token key control plane's Nacos client and the project's unified Nacos configuration and credential source. Review existing configuration, logging, timeout, retry, and test entry points before defining coverage for authentication failure and credential updates. Done means authenticated environments can create, read, and rotate keys without exposing credentials, with secure deployment documentation added.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- authentication, backend, documentation, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100