Support Username/Password OAuth Flow#780
Merged
cwarden merged 1 commit intoForceCLI:masterfrom May 8, 2026
Merged
Conversation
Add an OAuth Username/Password grant type alongside the existing SOAP
login since SOAP login will no longer be supported after Summer '27.
When --user and --password are provided, the login command now selects
between two flows:
- OAuth Username/Password flow when --connected-app-client-secret is
set. The client secret is included in the token request alongside
the client id, username, and password.
- SOAP login otherwise (preserving prior behavior). A deprecation
warning is written to stderr indicating SOAP login will be removed
after Summer '27 and pointing users to --connected-app-client-id /
--connected-app-client-secret for the OAuth flow.
When the OAuth password flow returns invalid_grant / "authentication
failure", append a hint to the error noting that only Connected Apps
support the username/password flow; External Client Apps do not.
cwarden
force-pushed
the
oauth-username-password
branch
from
4717003 to
e8790f7
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds an OAuth Username/Password grant type alongside the existing SOAP
login, since SOAP login will no longer be supported after Summer '27.
When --user is provided, the login command now selects between two flows:
OAuth Username/Password flow when --connected-app-client-secret is
set. The client secret is included in the token request alongside
the client id, username, and password.
SOAP login otherwise (preserving prior behavior). A deprecation
warning is written to stderr indicating SOAP login will be removed
after Summer '27 and pointing users to --connected-app-client-id /
--connected-app-client-secret for the OAuth flow.
When the OAuth password flow returns invalid_grant / "authentication
failure", append a hint to the error noting that only Connected Apps
support the username/password flow; External Client Apps do not.