Repository navigation
docs(research): connector, credential and egress layer audit (#13623) - #13647
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Thinking Path
Audit of our connector, credential and egress layer, using an external implementation of the same
problem domain as a comparison lens. The goal was to find real defects and structural gaps, not to
import a design — so every candidate pattern was checked against what we already have before being
proposed, and the most impressive idea in the reference was rejected because it does not fit our
scale.
What Changed
Docs only. No code touched.
docs/research/connector-credential-egress-audit.md— the auditdocs/research/_index.md— index entry.session/HANDOFF-issue-13623.md— session handoffFindings (all filed, none implemented)
Umbrella #13623 with children #13624-#13632, plus #13643 filed under #10088 Task 5.
Two live bugs, both in
knowledge/connectors/credential_store.py, both silent in production:expires_in(permitted by RFC 6749 §5.1) setsthe expiry to
None, and_access_token_expired(None)returnsFalse, so the credential isnever refreshed again. Connector auth dies days later with nothing in the logs pointing at the
refresh that caused it.
get_access_tokenis read → refresh → write with no lock. The code already notesthat some providers rotate the refresh token per use; a scheduled sync overlapping a
user-triggered one can strand the grant.
Two fail-open guards (#13628): the ownership check skips rather than denies on a missing
created_by, androtate()is the only credential read path that omitsaccessed_by, so the mostprivileged operation is the unaudited one.
Egress (#13624, #13625): cross-origin redirects replay the caller's
Authorizationheader; sixconnectors with user-configured hosts never touch the SSRF guard. #13625 is not a duplicate of
#13204, which covers browser paths only.
Secrets platform (#13643):
integrations/has no secrets-manager integration at all —credentials are passed as bare values, so no grant, audit, revocation, or dependency edge applies.
Verification
Docs-only change; no gates apply. Every claim in the document cites a file and line that was read,
and the two live bugs were traced through their call paths before filing.
Model Used
Claude Opus 5 (1M context)