-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sfdx force:auth:jwt:grant failing after 14/01 release #806
Comments
Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support. |
Hey, I'm reading that they changed auth into its own component. |
Hi @sifer, i'm aware of that change - however the command has been aliased for now so it "should" continue to work as before was my understanding? |
Update: changing our pipeline configuration to use "sfdx auth:jwt:grant" works - so it would appear to be the alias which is broken? |
Same here, we have several CIs broken, alias doesn't seem to work. |
I just took a look at our CI builds. Our builds update the CLI installation on the Docker image before working on the build. When I just checked on a build, it is upgrading to v7.84.2-a2868a68d5 .... not v7.83.0-eba9c6a927 that @anderg4. Has Salesforce already fixed this? It is odd because npmjs.com is still showing v7.83.1 as the "latest" (re: npmjs.com entry on 'sfdx-cli') |
Release process: an npm package goes at as For example, right now |
@mshanemc -- Understood, but how is my |
Sorry, we're not using npm. Our pipelines use wget to download the latest via: We've changed to use the non-aliased command |
CLI has been rolled back - see #811 |
Exact same issue has been re-introduced.
|
sfdx retrieved into github action via:
|
the above results in sfdx-cli-v7.83.0-eba9c6a927-linux-x64 which appears to be the original non-working version from above rather than the correct repackaged version from Feb 5 |
also note that we changed the URLs in early 2021, so you don't want to use that URLs discussed on this issue. ex: https://developer.salesforce.com/media/salesforce-cli/sfdx/channels/stable/sfdx-linux-x64.tar.gz You can always check the docs https://developer.salesforce.com/docs/atlas.en-us.232.0.sfdx_setup.meta/sfdx_setup/sfdx_setup_install_cli.htm#sfdx_setup_install_cli_macos |
Summary
Our AWS pipeline which has been working for months has just started failing to deploy to Production with a strange error message "No org configuration found for name".
Steps To Reproduce:
Expected result
Successful connect
Actual result
Error message and pipeline failure.
Additional information
sfdx installed to ·[38;5;104m/usr/local/bin/sfdx
sfdx-cli/7.83.0-eba9c6a927 linux-x64 node-v12.18.3
CMD= /usr/local/bin/sfdx force:auth:jwt:grant --clientid (redacted) --jwtkeyfile /tmp/server.key --username (redacted) --instanceurl https://login.salesforce.com
› Warning: force:auth:jwt:grant is not a sfdx command.
Did you mean auth:jwt:grant? [y/n]: {
"status": 1,
"name": "NoOrgFound",
"message": "No org configuration found for name (redacted)",
"exitCode": 1,
"commandName": "SourceDeployCommand",
"stack": "NoOrgFound: No org configuration found for name (redacted)\n at Function.create (/usr/local/lib/sfdx/node_modules/@salesforce/core/lib/sfdxError.js:160:16)\n at AuthInfo.loadAuthFromConfig (/usr/local/lib/sfdx/node_modules/@salesforce/core/lib/authInfo.js:682:49)",
"warnings": [
"The error message "NoOrgFound" has been deprecated and will be removed in v46 or later. It will become "NamedOrgNotFound"."
]
}
The text was updated successfully, but these errors were encountered: