Skip to content

fix(connectors): DataForSEO v2 reads DATAFORSEO_USERNAME (v0.459.1) - #866

Merged
vikasprogrammer merged 1 commit into
mainfrom
feat/dfs-v2-username
Oct 12, 2026
Merged

vikasprogrammer merged 1 commit into
mainfrom
feat/dfs-v2-username

Conversation

@vikasprogrammer

Copy link
Copy Markdown
Owner

dataforseo-mcp-server@2.9.13 reads its login only from DATAFORSEO_USERNAME; v3 reads DATAFORSEO_LOGIN (with a USERNAME fallback). The 0.458.0 v2 catalog entry set DATAFORSEO_LOGIN, so every v2 call returned HTTP 401.

  • v2 entry's login field is now DATAFORSEO_USERNAME, still filled from secret:DATAFORSEO_LOGIN, so one vault key serves both versions.
  • connector-auth-stub-test.cjs pins the per-version env var.
  • Runbook notes the difference for hand-built connectors.

Verified against the real API: v2 with DATAFORSEO_USERNAME → status 20000; with DATAFORSEO_LOGIN → 401.

🤖 Generated with Claude Code

dataforseo-mcp-server@2.9.13 only reads DATAFORSEO_USERNAME, so the v2
catalog entry from 0.458.0 sent no login and got HTTP 401 on every call.
The field now sets DATAFORSEO_USERNAME from the same secret:DATAFORSEO_LOGIN
vault key; v3 reads DATAFORSEO_LOGIN and is unchanged. Test pins the
per-version env var.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@vikasprogrammer
vikasprogrammer merged commit 72af4bd into main Oct 12, 2026
1 check passed
@vikasprogrammer
vikasprogrammer deleted the feat/dfs-v2-username branch October 12, 2026 08:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant