github / github/copilot-cli

Secure credential storage for HTTP MCP OAuth tokens

未關閉
#2,783 1 則留言 1 個 reaction 已指派 0 人 在 GitHub 檢視
area:authentication area:mcp
主要語言
Shell
星號
11.2k
分支
1.9k
平均合併
14 小時 16 分鐘
30 天內合併 PR
6

描述

### Describe the feature or problem you'd like to solve

The Copilot CLI currently persists OAuth access and refresh tokens as plaintext JSON files on disk (~/.copilot/mcp-oauth-config/*.tokens.json) when authenticating to HTTP-based MCP servers. This introduces several security concerns:
1. **Plaintext exposure** - Tokens stored as unencrypted JSON can be read by any process or user with filesystem access. This violates the principle of least privilege for credential storage.
2. **Cloud sync risk** - Many enterprise users sync their home directory or profile folders via OneDrive, Dropbox, or similar tools. Plaintext tokens in synced directories get uploaded to cloud storage, expanding the attack surface and triggering DLP/security policy violations.
3. **Credential persistence** - File-based tokens survive beyond their intended session lifetime. If a machine is compromised, an attacker gains access to cached tokens without needing to re-authenticate.
4. **Inconsistency with VS Code** - VS Code already handles MCP OAuth tokens securely through the OS Secret Storage API (Windows Credential Manager, macOS Keychain, libsecret on Linux). The CLI should follow the same pattern for consistency and security.

### Proposed solution

Leverage the OS-native credential/secret manager on each platform rather than writing tokens to disk. This aligns with security best practices, avoids DLP policy conflicts, and provides a consistent security posture across the Copilot toolchain.

### Example prompts or workflows

_No response_

### Additional context

_No response_

貢獻指南

開啟貢獻指南

研究方向

Start by locating the code that writes OAuth tokens to ~/.copilot/mcp-oauth-config/*.tokens.json. Review how the CLI authenticates to HTTP-based MCP servers and how VS Code uses OS Secret Storage, including Windows Credential Manager, macOS Keychain, and libsecret on Linux. Done means tokens no longer persist as plaintext files and are stored through native credential managers on each platform.

由索引模型根據 Issue 內容生成。

評估

技術堆疊
shell
領域
authentication, cli, security
Issue 類型
功能
難度
5/5
預估耗時
一週以上
活躍度
冷清
描述清晰度
基本清楚
新手友好度
38/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。