larksuite / larksuite/cli

支持通过个人 OAuth 访问企业组织资源

Open
#880 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

背景

目前 lark-cli 需要 App ID/Secret 配置企业自建应用才能使用。对于普通开发者而言:

  • 企业管理员出于安全考虑,不允许创建企业自建应用
  • 个人应用可以创建,但无法通过 OAuth 用户身份访问企业组织的资源
  • 开发者有自动化操作审批流、文档、多维表格等企业资源的需求

期望

希望提供一种方式,让开发者能够在没有企业应用的情况下:

  • 通过个人 OAuth 登录(User Access Token)
  • 以个人身份访问企业组织内自己有权限的资源(如自己创建的文档、所在的群聊、自己发起的审批等)

相关

  • 讨论:#234

使用场景

  • 自动化管理个人创建的文档和文件夹
  • 操作自己发起的审批流程
  • 管理个人有权访问的多维表格
  • 团队内部工具化场景(多个成员共用 CLI,但管理员不开放应用创建权限)

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

The issue names no files or tests; start by reading the existing App ID/Secret configuration and related discussion #234. Define the personal OAuth flow and its resource-access boundaries, then verify that users can authenticate without an enterprise app and access only resources permitted to their personal identity.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
authentication, cli
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.