Windows keyring error recommends cf auth login --use-keyring, which isn't a valid option
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- Half a day
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- nodejs, typescript
- Domain
- authentication, cli
Research direction
Start from windowsBindingMissingMessage and secretToolMissingMessage in the shared workers-auth code, which build the cf auth login --use-keyring advice, and from setKeyringPreference, which no command exposes. Reproduce with CLOUDFLARE_AUTH_USE_KEYRING=true and no @napi-rs/keyring installed. Done means the message points only at options cf actually accepts, and that choice is agreed with maintainers first.
Written by the indexing model from the issue text.
Description
Summary of the issue
On Windows, when CLOUDFLARE_AUTH_USE_KEYRING=true is set and @napi-rs/keyring isn't installed, any non-interactive auth command fails with:
Run `cf auth login --use-keyring` interactively to install it automatically, …
Or disable keyring storage: `cf auth login --no-use-keyring`.
cf auth login doesn't define --use-keyring or --useKeyring, so following the advice gives an unknown-argument error. The text comes from windowsBindingMissingMessage(loginCommand) in the shared workers-auth code, and the flag only exists in wrangler. In cf, keyring storage is controlled only by CLOUDFLARE_AUTH_USE_KEYRING or the stored keyring_enabled preference. setKeyringPreference exists, but no command exposes it. secretToolMissingMessage (Linux) has the same problem.
Related:
- The fallback lookup uses
npm root -g, so a global install made through Volta (and probably other version managers) is never found, even though the message suggestsnpm install -g. defaultNpmRunnerusesshell: trueonly on win32, which triggers Node 26's DEP0190 warning.
Expected behaviour
Suggested fix:
either add --use-keyring/--useKeyring to cf auth login, or pass cf-specific wording, such as setting CLOUDFLARE_AUTH_USE_KEYRING, into these messages.
Version of cf used
v1.0.0-beta.17
System information and package versions
Windows 10
Node 26.1.0
npm: 11.17.0
Reproduction (optional)
Run in PowerShell:
$env:CLOUDFLARE_AUTH_USE_KEYRING="true"; cf auth whoami < NUL
Relevant error logs (optional)
No response
- Dominant language
- TypeScript
- Stars
- 853
- Forks
- 42
- Avg merge
- 17h 57m
- Merged PRs (30d)
- 146
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from cloudflare/cf
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
cloudflare/cf#344 ·
Maintainers usually reply within 1 day
-
upstream
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
cloudflare/cf#262 ·
Maintainers usually reply within 1 day
-
`cf dev` rejects `--port` and `--host` for Vite projects, including the `cf init` templatePossibly taken @jamesopstad claimed this 5 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
cloudflare/cf#223 · 2 assignees ·
Maintainers usually reply within 1 day
-
upstream
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
cloudflare/cf#179 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 58/100
cloudflare/cf#347 ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
paperclipai/paperclip#16785 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
code-yeongyu/senpi#3661 ·
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 78/100
lingdojo/kana-dojo#32731 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
bug status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
mastra-ai/mastra#27538 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Yeachan-Heo/oh-my-codex#3822 ·
Maintainers usually reply within 1 day