Frequent AuthDecryptError on all connected orgs

[dpr-nh]

Summary

While working, I'm deploying frequently to a sandbox and will be running the same deploy command multiple times. At some point I will get this error seemingly at random:

Error (2): Parsing --target-org 
        Failed to decipher auth data. reason: Unsupported state or unable to authenticate data.
See more help with --help

After this happens, I check my connected orgs using sf org list and see that every single one has the same AuthDecryptError status. It's not just the org I was working on, it's all my connected orgs getting disconnected at the same time.

This problem happens multiple times a day. I'm not sure if this is a bug with the sf CLI or Salesforce itself, hoping you can point me in the right direction.

Steps To Reproduce

I honestly do not know how to reproduce this. It happens what seems totally randomly.

System Information

{
  "architecture": "linux-x64",
  "cliVersion": "@salesforce/cli/2.44.8",
  "nodeVersion": "node-v20.11.0",
  "osVersion": "Linux 6.10.8-200.fc40.x86_64",
  "rootPath": "/home/dpr/.nvm/versions/node/v20.11.0/lib/node_modules/@salesforce/cli",
  "shell": "zsh",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 3.0.18 (core)",
    "@oclif/plugin-commands 3.3.4 (core)",
    "@oclif/plugin-help 6.0.22 (core)",
    "@oclif/plugin-not-found 3.1.10 (core)",
    "@oclif/plugin-plugins 5.1.3 (core)",
    "@oclif/plugin-search 1.0.24 (core)",
    "@oclif/plugin-update 4.2.14 (core)",
    "@oclif/plugin-version 2.1.2 (core)",
    "@oclif/plugin-warn-if-update-available 3.0.19 (core)",
    "@oclif/plugin-which 3.1.10 (core)",
    "@salesforce/cli 2.44.8 (core)",
    "apex 3.1.13 (core)",
    "auth 3.6.17 (core)",
    "community 2.3.14 (user) published 382 days ago (Sat Aug 26 2023) (latest is 3.2.30)",
    "data 3.4.3 (core)",
    "deploy-retrieve 3.8.3 (core)",
    "info 3.3.3 (core)",
    "limits 3.3.9 (core)",
    "marketplace 1.2.8 (core)",
    "org 4.1.14 (core)",
    "packaging 2.4.5 (core)",
    "schema 3.3.9 (core)",
    "settings 2.2.7 (core)",
    "sobject 1.4.6 (core)",
    "source 3.3.18 (core)",
    "telemetry 3.3.11 (core)",
    "templates 56.2.9 (core)",
    "trust 3.7.3 (core)",
    "user 3.5.11 (core)"
  ]
}

[github-actions]

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.

[github-actions]

Hello @dpr-nh 👋 None of the versions of sf you shared match the latest release.

Shared: 2.44.8
Latest: 2.57.7

Update to the latest version of Salesforce CLI (docs) and confirm that you're still seeing your issue.
You can also try the rc and nightly releases! (docs)

After updating, share the full output of sf version --verbose --json

[iowillhoit]

This looks similar to this issue: #2174

Are you using KWallet?

Update to the latest version of the CLI (currently 2.58.7) and try setting this env var: SF_USE_GENERIC_UNIX_KEYCHAIN=true
Details here: #2174 (comment)

[github-actions]

Hello @dpr-nh 👋 None of the versions of sf you shared match the latest release.

Shared: 2.44.8
Latest: 2.58.7

Update to the latest version of Salesforce CLI (docs) and confirm that you're still seeing your issue.
You can also try the rc and nightly releases! (docs)

After updating, share the full output of sf version --verbose --json

[shetzel]

I would run sf doctor as well and note the diagnostic tests around v2 crypto. Changing the encryption key without complete support from all installed plugins may cause decryption problems.

[dpr-nh]

Hi @iowillhoit,

I'm not using KWallet.
I've updated my CLI and set the env variable. I'll let you know if I get the problem again.

[dpr-nh]

Haven't had the problem since so either updating or setting the env variable fixed the issue.

[github-actions]

Hello @dpr-nh 👋 None of the versions of sf you shared match the latest release.

Shared: 2.44.8
Latest: 2.59.6

Update to the latest version of Salesforce CLI (docs) and confirm that you're still seeing your issue.
You can also try the rc and nightly releases! (docs)

After updating, share the full output of sf version --verbose --json

[0cv]

Bug is still here but setting SF_USE_GENERIC_UNIX_KEYCHAIN is indeed workarounding successfully the issue ...

[github-actions]

Hello @dpr-nh 👋 None of the versions of sf you shared match the latest release.

Shared: 2.44.8
Latest: 2.61.8

Update to the latest version of Salesforce CLI (docs) and confirm that you're still seeing your issue.
You can also try the rc and nightly releases! (docs)

After updating, share the full output of sf version --verbose --json