Misleading auth errors: CLOUDFLARE_PROFILE ignored, a missing --profile reported as "No authentication token found", a wrong account id as "Authentication error"
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- api, authentication, cli
Research direction
Start by reproducing the three cf workers list cases and compare them with cf auth whoami; inspect the profile and environment-variable handling referenced by related issue #37. Use FINDINGS.md and the findings/ directory for context. Done means the profile behavior is supported or documented, missing profiles are named, and account-id 403s point users toward checking the account id.
Written by the indexing model from the issue text.
Description
cf version: 1.0.0-beta.5, macOS
Three auth and config mistakes produce errors that point the wrong way:
CLOUDFLARE_PROFILEis ignored.CLOUDFLARE_PROFILE=nosuchprofile cf workers list --per-page 1succeeds with the default credentials. It neither uses nor rejects the profile.- A missing profile reads like a missing login.
cf workers list --profile nosuchprofilegivesNo authentication token found.instead of "profile nosuchprofile not found (available: ...)". - A wrong account id reads like a bad token.
CLOUDFLARE_ACCOUNT_ID=00000000000000000000000000000000 cf workers listgives[10000] Authentication error(403). The token is fine; the account id isn't one the token can access.
Expected:
- honour
CLOUDFLARE_PROFILE, or document that it isn't supported; - name the missing profile;
- for a 403 on an
/accounts/{id}path, suggest checking the account id (e.g. againstcf auth whoami).
Related: #37 (document supported environment variables).
Found while evaluating cf for a dev workflow: https://github.com/joeblew999/cf-cli-test (FINDINGS.md, findings/).
- 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
-
The inspector never shows the instances field, so scaling out is unreachablePossibly taken @Mrkewl claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
xevrion/breakscale#96 ·
Maintainers usually reply within 4 days
-
Object parameters lose their structure when resources is enabledPossibly taken @asts-top claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
rossant/awesome-math#199 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
jaegertracing/jaeger-ui#4618 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
mifi/lossless-cut#3125 ·
Maintainers usually reply within 1 day