Skip to content

Frequent Authentication Error #3572

Open

Description

@tannerrobinaugh

Expected result

Running a deployment or retrieval command results in the metadata being deployed or retrieved.

Actual result

Running a deployment or retrieval command results in "No default environment found. Use -o or --target-org to specify an environment."
Running with those flags results in "Failed to decipher auth data. reason: Unsupported state or unable to authenticate data."

Additional information

This issue just started today. I was not on the most recent version of the CLI, however updating has not fixed it. I have removed my existing connections and reestablished them which fixed the issue for about an hour but then it came back.

System Information

CLI:
@salesforce/cli/2.137.7 linux-x64 node-v22.22.3

Plugin Version:
@oclif/plugin-autocomplete 3.2.50 (core)
@oclif/plugin-commands 4.1.55 (core)
@oclif/plugin-help 6.2.49 (core)
@oclif/plugin-not-found 3.2.86 (core)
@oclif/plugin-plugins 5.4.69 (core)
@oclif/plugin-search 1.2.50 (core)
@oclif/plugin-update 4.7.43 (core)
@oclif/plugin-version 2.2.46 (core)
@oclif/plugin-warn-if-update-available 3.1.65 (core)
@oclif/plugin-which 3.2.55 (core)
@salesforce/cli 2.137.7 (core)
agent 1.40.5 (core)
apex 3.9.31 (core)
api 1.3.36 (core)
auth 4.4.1 (core)
code-analyzer 5.13.0 (user)
data 4.0.103 (core)
deploy-retrieve 3.24.50 (core)
info 3.4.136 (core)
limits 3.3.91 (core)
marketplace 1.3.28 (core)
org 5.11.4 (core)
packaging 2.28.3 (core)
schema 3.3.115 (core)
settings 2.4.82 (core)
sobject 1.4.110 (core)
telemetry 3.8.23 (core)
templates 56.17.7 (core)
trust 3.8.11 (core)
user 3.10.1 (core)
SF ENV. VARS.
SF_BINPATH,/home/tannerrobinaugh/.local/share/sf/client/bin/sf
SF_AUTOUPDATE_DISABLE,true
SF_DISABLE_AUTOUPDATE,true
SF_UPDATE_INSTRUCTIONS,Use "npm update --global @salesforce/cli" to update npm-based installations.
Windows: false
Shell: bash
Channel: stable

Diagnostics

✅ pass - salesforcedx plugin isn’t installed
✅ pass - you don't have any linked plugins
✅ pass - [@salesforce/plugin-trust] can ping: https://registry.npmjs.org
✅ pass - [@salesforce/plugin-trust] can ping: https://registry.yarnpkg.com
✅ pass - [@salesforce/plugin-trust] can ping: https://registry.npmjs.org/
✅ pass - using latest or latest-rc CLI version
✅ pass - [@salesforce/plugin-deploy-retrieve] sourceApiVersion matches apiVersion
✅ pass - can access: https://test.salesforce.com
✅ pass - can access: https://appexchange.salesforce.com/services/data
✅ pass - can access: https://developer.salesforce.com/media/salesforce-cli/sf/channels/stable/sf-win32-x64-buildmanifest
✅ pass - [@salesforce/plugin-auth] CLI supports v2 crypto

Activity

  1. iowillhoit commented on Jun 8, 2026

    @iowillhoit
    Contributor

    How are you establishing your org connection? We recently made some changes to remove sensitive values from certain commands (like sf org display) see #3560

  2. stephenlf commented on Jun 18, 2026

    @stephenlf

    I just ran into this same problem. I'm using Arch Linux. Perhaps it's an issue connecting to the decryption key store? gnome-keyring or secret-tool? I was messing around with those tools earlier. We'll see if it survives a reboot.

  3. renatoliveira commented on Aug 11, 2026

    @renatoliveira

    I started having this too. Turned out that purging the global config json file and credentials "solved" the issue of not being able to use any command of the CLI.

    After signing in to two different environments I still get AuthDecryptError errors when using sf org open but not sf org list, for example.

    Setting the environment variable SF_USE_GENERIC_UNIX_KEYCHAIN to true then solved the issue for me and I can open orgs normally now.

  4. soridalac commented on Oct 20, 2026

    @soridalac
    Member

    Hi @tannerrobinaugh and @stephenlf, this is a known issue on linux and same root cause to #3018 . We have the workaround by setting this env SF_USE_GENERIC_UNIX_KEYCHAIN=true as renatoliveira mentioned above. Let me know if this doesn't resolve it for you all. Thanks!

  5. stephenlf commented on Oct 26, 2026

    @stephenlf

    That works. Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions