[FEATURE] Support Oauth remote device flow for headless environments

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

阅读 docs/OAUTH2.md,尤其是 OAuth2 future-enhancements 部分,然后跟踪 pup auth login 入口点及其当前的浏览器流程。完成的标准是:远程登录能够为单独的本地浏览器提供一个 URL,在不重定向到本地 Web 服务器的情况下完成授权,并让 pup 做好使用准备。

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

描述

authnz enhancement usability

Is your feature request related to a problem?

I want to run the Oauth flow within a remote environment without access to a web browser. This is currently listed as an enhancement for the Oauth2 auth.

Describe the solution you'd like

After running pup auth login (within a remote environment) I want to get a URL that I'll follow inside my local box. Optionally, the auth flow should check and confirm whether I'm logging from pup at some point.

After a successful login, I expect the web browser to show me a message like

"pup vx.y.z was successful authorized, you can now close this tab.

and pup should be ready to use without any redirects to a local web server.

Describe alternatives you've considered

The alternatives here are PATs or API Keys, but having a Oauth device flow would bring to pup feature parity between with other CLIs that I use in the same remote environment.

Additional context

I think that aws-cli offers a experience similar to what I want for pup

Proposed command syntax (if applicable)

pup auth login --remote-device

or alternatively

pup auth login --no-browser
主要语言
Rust
星标
1k
派生
138
平均合并
17 小时
30 天内合并 PR
82

环境准备

从这里开始

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

DataDog/pup 的其他 Issue

查看 DataDog/pup 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

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