Skip to content

sf org login jwt takes a very long time to complete #3626

Description

@rubicn

Summary

sf org login jwt takes a very long time to complete.

We are using JWT authentication in our CI/CD pipelines, and the authentication step can take a significant amount of time before completing.

We initially investigated this while upgrading to Salesforce CLI 2.147.7 (August 12, 2026). However, the long execution time is also present in previous CLI versions, so this does not appear to be a regression specific to 2.147.7.

Steps To Reproduce
Authenticate to a Salesforce org using JWT:
sf org login jwt
--client-id <CLIENT_ID>
--jwt-key-file <JWT_KEY_FILE>
--username
--instance-url https://login.salesforce.com
Measure the time required for the command to complete.
Repeat the command using different Salesforce CLI versions.
Expected result

sf org login jwt should complete within a reasonable amount of time.

Actual result

sf org login jwt takes a very long time to complete.

The issue is especially noticeable in CI/CD environments where JWT authentication is performed frequently.

We initially noticed this while testing Salesforce CLI 2.147.7, which includes changes related to JWT authentication and scratch org creation, but we confirmed that the long execution time also occurs with previous CLI versions.

Additional information

Salesforce CLI version tested:

2.147.7 — August 12, 2026

The 2.147.7 release notes mention changes related to JWT authentication:

We added two environment variables to fix an issue where org create scratch fails when you authenticate the associated Dev Hub with an external client app via JWT (org login jwt).

It would be useful to understand whether the long execution time is expected behavior, or whether there is an unnecessary delay in the JWT authentication flow.

System Information
PASTE OUTPUT OF:
sf version --verbose --json

Shell:

PASTE SHELL INFORMATION HERE
CLI Doctor
PASTE OUTPUT OF:
sf doctor
Reproduction repository

A repository is not required to reproduce this issue because the problem occurs directly with the sf org login jwt command and does not depend on project-specific source code.

Metadata

Metadata

Assignees

No one assigned

    Labels

    more information requiredIssue requires more information or a response from the customer

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions