Salesforce "No authorization information found for ..." in CI

A command tried to use a username or alias that the CLI has no stored auth for. CLI auth lives in the home directory and does not carry between fresh runners or isolated jobs, so a missing or non-persisted login is the usual cause.

What this error means

A deploy or query step fails with "No authorization information found for <alias>" even though an earlier step or local machine logged in.

Error (1): No authorization information found for ci-org.

Common causes

The login ran in a different job or runner

Each runner starts clean. If the JWT login happened in another job, or the auth state was not persisted, the alias is unknown in this step.

The alias name does not match

The command references an alias that was never set, or is spelled differently than the --alias used at login.

How to fix it

Authenticate in the same job before using the org

1. Run sf org login jwt (or set an auth URL) in the same job that deploys.
2. Use the exact alias from login in every later command via --target-org.
3. Verify with sf org list before the deploy step.

sf org login jwt --alias ci-org ...
sf org display --target-org ci-org

Re-auth from a stored SFDX auth URL

Persist a stored auth URL as a secret and use it to log in non-interactively each run.

echo "$SF_AUTH_URL" > authurl.txt
sf org login sfdx-url --sfdx-url-file authurl.txt --alias ci-org

How to prevent it

• Authenticate inside each job that needs the org; do not assume shared state.
• Use one consistent alias and pass --target-org explicitly.
• Verify auth with sf org list early so failures surface before deploy.

Related guides