REST: sign in with a device code (pivotkit login, pivotkit token, curl/PowerShell)

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
javascript, powershell

调研方向

Start by reading the REST service's OAuth metadata handling, CLI command structure, and the “Server in 5 minutes” token instructions. The issue leaves a key design choice open: whether to provide documented curl/PowerShell steps or a REST endpoint, and calls for provider-specific checks across Authentik, Keycloak, and Microsoft Entra ID. Done means the chosen device flow supports token refresh and the setup guide offers the new login path.

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

描述

area:server enhancement

I want people to use the REST service with curl or PowerShell without asking me for a token.

  • pivotkit login --url <server> reads the REST resource's metadata (/.well-known/oauth-protected-resource), runs the OAuth 2.0 device authorization grant against the server's issuer, and keeps the refresh token in the OS keychain (a 0600 file where there is none). pivotkit token prints a fresh access token: curl -H "Authorization: Bearer $(pivotkit token)".
  • The same without the CLI: documented curl/PowerShell steps (start the device flow, open the URL, poll for the token), or a small REST endpoint that does the device flow for the caller. Decide which.

To check per provider (in their current docs): Authentik (device code flow per brand, public client, device endpoint in discovery, per-application issuer, audience, refresh with offline_access); Keycloak (the per-client "OAuth 2.0 Device Authorization Grant" switch, audience mapper); Microsoft Entra ID (public client flows, devicecode endpoint, api://<app>/.default, v2 tokens, Conditional Access that may block device code, group overage). The "Server in 5 minutes" page's token step should then offer pivotkit login too.

主要语言
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 摘要。