Skip to content

fix(connector): a placeholder API key is not a connection#271

Merged
AVADSA25 merged 1 commit into
mainfrom
fix/placeholder-headers
Jul 16, 2026
Merged

fix(connector): a placeholder API key is not a connection#271
AVADSA25 merged 1 commit into
mainfrom
fix/placeholder-headers

Conversation

@AVADSA25

Copy link
Copy Markdown
Owner

Caught in the live output right after #270 deployed:

github  auth=api_key  enabled=True  connected=True   ← false

GitHub holds the literal string "Bearer <GITHUB_TOKEN>". is_connected used bool(headers), so a placeholder counted as configured and the card claimed "Connected via API key" with no key at all.

Same class of lie as the old Hugging Face "Connected", one step removed. #270 didn't create it — stripe shipped with "Bearer <STRIPE_KEY>" and would have claimed Connected the moment it was enabled — but repairing github to api_key made it visible.

A header value containing <…> is a placeholder, not a key.

Case Result
Bearer <GITHUB_TOKEN> not connected ✅
Bearer <STRIPE_KEY> not connected ✅
Bearer ghp_realvalue123 connected ✅
no headers / empty headers not connected ✅
real key + X-Note: a>b connected ✅ (no false negative)
two headers, one still a placeholder not connected ✅

Manifest regenerated.

The seeded api_key entries ship placeholders — {"Authorization": "Bearer
<STRIPE_KEY>"} — and is_connected used bool(headers), so a connector with no
key at all reported "Connected via API key". #270 made this visible by
repairing github to api_key: the card immediately claimed Connected while
holding the literal string "<GITHUB_TOKEN>".

Same class of lie as the old Hugging Face "Connected", one step removed.
A header value containing <...> is a placeholder, not a key.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@AVADSA25
AVADSA25 merged commit 9aff07f into main Jul 16, 2026
1 check passed
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.

2 participants