server: short-lived bearer tokens without a sign-in provider

未关闭
#485 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
活跃
技术栈
cli, javascript

调研方向

Start by reading how the server handles static bearer tokens from auth.tokens for REST and MCP, and how the pivotkit-server CLI is structured. The issue proposes a CLI for creating expiring tokens but leaves key storage, rotation, revocation, protocol support, logging, and limits open. First settle those design questions; done means the token lifecycle and acceptance behavior are defined and tested.

由索引模型根据 Issue 内容生成。

描述

area:server enhancement

Without a sign-in provider, REST and MCP use static bearer tokens (auth.tokens, from a variable or a file, one profile each). That covers many setups (a read-only token per client), but the token never expires and the operator has to create and hand it out by hand.

Idea: let the operator issue short-lived tokens without an identity provider, e.g. pivotkit-server token create --profile <name> --expires 1h signed with a server key, checked like a static token but with an expiry, optionally named for the log. A token page in a web UI would need a signed-in person, which is what a sign-in provider gives, so the CLI path comes first.

Questions to settle before building: key storage and rotation, revoking a token before it expires, whether REST and MCP both accept it, and how it shows in logs and limits.

主要语言
JavaScript
星标
1
派生
1
平均合并
3 小时 34 分钟
30 天内合并 PR
213

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

eizedev/pivotkit 的其他 Issue

查看 eizedev/pivotkit 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。