Security changes to the default CLI Connected App (`PlatformCLI`)
まだ誰も着手していません。
評価
- 難易度
- 1/5
- 見積もり時間
- 1時間未満
- 初心者へのやさしさ
- 1/100
- issue の種類
- ドキュメント
- 明瞭さ
- 明確に書かれている
- 活発さ
- 活発
- 技術スタック
- javascript
- 領域
- cli
調査の方向性
This issue describes upcoming OAuth policy changes for the default PlatformCLI Connected App and gives no files, tests, or code entry points to change. Start by reading the linked PKCE and jsforce references; done means users understand which login flows are affected, when each change takes effect, and what action to take.
索引モデルが issue の本文から書いたものです。
説明
We're enabling two OAuth security controls on PlatformCLI, the Connected App the CLI uses by default when you run sf org login web without your own --client-id. They roll out on two dates:
- PKCE required for web login — enabled October 21, 2026.
- 30-day refresh-token idle timeout — enabled November 9, 2026.
Most people on a current CLI will notice nothing. Here's what's changing and who might be affected.
1. PKCE is now required for web login (October 21, 2026)
PKCE is a standard that binds an authorization request to the client that started it, so an intercepted auth code can't be redeemed by anyone else. The Salesforce CLI has sent a PKCE challenge on sf org login web for years. This change makes the server reject any web-login request that arrives without one.
Who might be affected:
- Very old CLI versions. Releases from roughly late 2021 through March 2024 shipped a version of our auth library that did not send a PKCE challenge. Running
sf org login web(orsfdx force:auth:web:login) on one of those builds against the default Connected App will now fail at the login step withinvalid_request / missing code challenge error.- Fix: Update to a current CLI.
- Custom integrations that authenticate against this Connected App without going through the Salesforce CLI or
@salesforce/core. If you built your own web/authorization-code flow (for example, a tool that drives OAuth directly) against the default Connected App, it must now send acode_challenge.- Fix: If you use jsforce directly, construct
OAuth2withuseVerifier: true. jsforce then generates a PKCE verifier and adds thecode_challengeto the authorization request (andcode_verifierto the token exchange) for you.
- Fix: If you use jsforce directly, construct
- Note: This only affects the interactive web login flow. JWT, access-token, and sfdx-url logins do not use PKCE and are unaffected.
- Note: If you use your own Connected App via
--client-id, this setting does not apply to you. Your Connected App's own configuration governs.
2. Refresh tokens will expire after 30 days of inactivity (starting November 9, 2026)
Starting November 9, 2026, the default Connected App has an idle timeout of 30 days on refresh tokens. If a refresh token is not used to get a new access token for 30 consecutive days, it is invalidated server-side and you'll be asked to log in again. Because the change applies going forward, the earliest an idle token can expire is early December 2026.
Who might be affected:
- This affects login flows that hold a refresh token, namely
webandsfdx-url. JWT logins (common in CI) re-sign on every call and are not affected. - In practice, any CLI used at least once a month keeps its refresh token alive, so active users should rarely see this. You'd notice it only on an org you haven't touched in over a month, where the fix is simply to run
sf org login webagain. - Note: The 30-day idle clock resets only when the access token expires and your refresh token is used to acquire a new access token from the server.
Questions or concerns?
Please comment on this Issue. We're happy to help you find the right path forward.
- 主要言語
- 言語のデータがありません
- スター
- 574
- フォーク
- 80
- 平均マージ
- 14時間 43分
- マージ済み PR（30日）
- 5
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートなし
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
forcedotcom/cli のほかの issue
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 74/100
forcedotcom/cli#3672 · コメント 3 件 ·
-
sf agent mcp asset replace --assets null throws raw TypeError instead of InvalidShape対応中かも @konkonrong-lgtm が 77 日前に担当しました。 オープンarea:afdx bug investigating owned by another team validated
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
forcedotcom/cli#3625 · コメント 4 件 ·
-
area:afdx bug owned by another team
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
forcedotcom/cli#3608 · コメント 2 件 ·
-
難易度 3/5 1〜2日 初心者へのやさしさ 68/100
forcedotcom/cli#3670 · コメント 1 件 ·
-
bug investigating validated
難易度 3/5 1〜2日 初心者へのやさしさ 66/100
forcedotcom/cli#3667 · コメント 5 件 ·
forcedotcom/cli の issue をすべて見る
似ている issue
-
area: parser bug difficulty: easy
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
hayagrivai-labs/phantom#150 ·
メンテナーはふだん 1 日以内に返信
-
difficulty: easy good first issue help wanted mentor available testing
難易度 1/5 1〜3時間 初心者へのやさしさ 88/100
hayagrivai-labs/sciproof#173 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 77/100
メンテナーはふだん 1 日以内に返信
-
Pills' meter dots fade on bright and deep pills対応中かも @wassim-azi が今日担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 75/100
wassim-azi/agy-powerline#168 ·
メンテナーはふだん 1 日以内に返信
-
enhancement good first issue
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
akobirjontulqinovfuture/keelyard#16 ·
メンテナーはふだん 13 日以内に返信