Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 21, 12:15 UTC
docs: explain token custody architecture and deployment options (#4446)
## Summary Security evaluations interpreted connected-account credential fields as a token-export path and conflated keeping tokens out of application code with keeping them outside Composio's custody. Add an architecture guide that explains those boundaries and distinguishes hosted custody from private deployments and customer-managed keys. ## Changes - Add `/docs/security/token-custody` with an OAuth/execution diagram, Python and TypeScript Proxy Execute examples, default API redaction, execution paths, deployment options, and authorization and retention responsibilities. - Replace the connected-account credential-printing examples with guidance on redacted authentication state and server-side execution. - Add the guide to security navigation and link it from the security and authentication pages. ## Type of change - [x] Documentation ## How Has This Been Tested? From `docs/`: - `bun run build`: passed, including TypeScript checking and static page generation. An existing Turbopack file-tracing warning remains. - `bun test tests/static/content.test.ts tests/static/navigation.test.ts tests/static/dashboard-links.test.ts tests/static/product-navigation.test.ts`: 24 passed. - `bun run lint:links`: no errors. - `bun run lint`: passed with warnings in unchanged files. Also compiled all changed MDX files, validated the page route and Mermaid diagram, and verified the SDK examples against their method signatures and parsed the Python example for syntax errors. No live provider request was made. ## Checklist - [x] Linters and focused tests passed locally. - [x] Documentation updated. - [x] Existing documentation checks cover this content-only change; no new tests needed. - [x] No changeset needed because no published package changes. ## Additional context Addresses Gauge action `cmtvykziy00300jxgg1i6j149`. Inspected details, insights, logs, and diffs for both evidence runs: - [Arcade comparison](https://agents.withgauge.com/composio-aclx/runs/cmtvo4yfd01gk0iuq0rdco72u): inferred an unmasking path from `account.state.val` without evidence that the API returned usable tokens. - [Nango comparison](https://agents.withgauge.com/composio-aclx/runs/cmtvo51xm01i20iuq6s4emlq3): treated application credential isolation and ownership of the token store as the same requirement. Deployment claims link to current Composio sources, including the published customer-managed key architecture. This PR documents behavior; it does not change credential handling.
No changes.