Fail to authenticate with JWT

[yongabyte]

Orb Version
The version number of the orb
2.1.0 and 2.0.0

Describe the bug

Workflows started failing around noon EST.

Workflows with the default - sfdx/install flag failed to authenticate to Dev orgs. The reason we found was that
the force:auth:jwt:grant command is dead on sfdx-cli versioned 7.83 (the current default version).

To Reproduce
In the workflow:

1. uses the default sfdx install option- sfdx/install
2. uses JWT as authentication method
3. see error

 ›   Warning: force:auth:jwt:grant is not a sfdx command.
Did you mean auth:jwt:grant? [y/n]: 

Expected behavior

The workflow will error out on any command in the run step if the workflow looks something like this

jobs:
  install_authenticate:
    executor: sfdx/default
    steps:
      - checkout
      - sfdx/install
      - sfdx/auth:
          defaultusername: x
      - run:
          command: 
            any sfdx cli commands

For us it was verify the default user name with sfdx force:config:set defaultusername=x and we got following error.

ERROR running config:set:  No AuthInfo found for name x

Additional context

Current workaround is to specify the sfdx-cli version installed with the orb.

      - sfdx/install:
          version: '7.82.0'

[pushyka]

Seeing this too. Thanks for suggesting the workaround @yongabyte
See also: forcedotcom/cli#787

[engineerakki]

Facing same issue.

› Warning: force:auth:jwt:grant is not a sfdx command.
Did you mean auth:jwt:grant? [y/n]:

[paulca99]

We're using AWS Codebuild in a pipeline , and using wget https://developer.salesforce.com/media/salesforce-cli/sfdx-linux-amd64.tar.xz to download sfdx. How do we get the previous version ?

[gmemstr]

Interesting - taking a look folks.

[gmemstr]

According to https://github.com/forcedotcom/cli/blob/main/releasenotes/README.md#50133-january-14-2021---cli-7842, the command was not removed, but is no longer aliased. Working on a fix.

[engineerakki]

Hi @paulca99
We use CircleCI SFDX orb and it seems that even our CircleCI orb pulls https://developer.salesforce.com/media/salesforce-cli/sfdx-linux-amd64.tar.xz

We moved to
sfdx auth:jwt:grant from

sfdx force:auth:jwt:grant

in our workflow and things started to run for us.

[pushyka]

Looks like over the weekend https://developer.salesforce.com/media/salesforce-cli/sfdx-linux-amd64.tar.xz has been reverted to 7.82.0 version

forcedotcom/cli#811

--2021-01-17 00:05:32--  https://developer.salesforce.com/media/salesforce-cli/sfdx-linux-amd64.tar.xz
Resolving developer.salesforce.com (developer.salesforce.com)... 151.101.201.145
Connecting to developer.salesforce.com (developer.salesforce.com)|151.101.201.145|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 22101004 (21M) [application/x-tar]
Saving to: 'sfdx-linux-amd64.tar.xz'

sfdx-linux-amd64.ta 100%[===================>]  21.08M  --.-KB/s    in 0.1s    

2021-01-17 00:05:32 (207 MB/s) - 'sfdx-linux-amd64.tar.xz' saved [22101004/22101004]

sfdx installed to /usr/local/bin/sfdx
sfdx-cli/7.82.0-3d0c527ac6 linux-x64 node-v12.18.3
CircleCI received exit code 0