larksuite / larksuite/cli

新版本出现lark-cli auth login: device authorization failed: Device authorization failed: The request is missing a required parameter: client_secret

Open
#1,932 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug domain/auth domain/core
Dominant language
Go
Stars
17.3k
Forks
1.4k
Avg merge
2d 4h
Merged PRs (30d)
105

Description

https://github.com/larksuite/cli/issues/509

Hi there,

同样的问题在最新版本的lark-cli又遇到了:

在公司内网部署的,需要配置http_proxy才能解析公网dns。配置了相关http_proxy的环境变量。

先执行lark-cli config init --new能够成功创建并配置新的飞书app

然后执行lark-cli auth login后报错

摘要:
域: sheets
权限: 常用权限
Scopes (7): docs:document:export, drive:file:download, sheets:spreadsheet.meta:read, ...

[lark-cli] [WARN] proxy detected: https_proxy=http://***@10.187.197.10:8080/ — requests (including credentials) will transit through this proxy. Set LARK_CLI_NO_PROXY=1 to disable proxy.
{
"ok": false,
"error": {
"type": "auth",
"message": "device authorization failed: Device authorization failed: The request is missing a required parameter: client_secret."
}
}

之前issue (https://github.com/larksuite/cli/issues/509) 中解决了,新版本又出现了,想问下这个有什么解决办法吗?

十分感谢!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing lark-cli config init --new and lark-cli auth login with the reported http_proxy environment variables, then trace the CLI's device-authorization and proxy-handling entry points. No file or test is named; done means login succeeds in the described proxy setup and the failure is covered by an appropriate regression check.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
authentication, cli, networking
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.