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, 23:30 UTC
docs(changelog): mask tokens for Composio-managed auth configs (#3242)
# Description Changelog entry for [SEC-331](https://linear.app/composio/issue/SEC-331/do-not-return-accessrefresh-tokens-for-default-auth-configs) / [hermes#9497](https://github.com/ComposioHQ/hermes/pull/9497). Communicates a single change: access tokens, refresh tokens, and the `Authorization` header are now always masked in `connected-accounts` API responses for connections created through Composio-managed auth configs — regardless of the project's `mask_secret_keys_in_connected_account` flag. Connections on customer-owned auth configs are unchanged. ## Structure - **Lead + triage.** Direct statement of the change, followed by "Most integrations need no changes" with the two cases where nothing changes (SDK / Tool Router / MCP; customer-owned auth configs). - **What is a Composio-managed auth config?** Reader concept primer and how to identify one (`auth_config.is_composio_managed`). - **Why this change.** One paragraph — shared OAuth app means shared outcomes from provider enforcement. No blame language, no self-critical "we used to…" framing. - **Example.** Before/after JSON of a Gmail connection with project masking disabled. - **Affected endpoints.** Three links to the API reference. - **If you need raw tokens.** Migration path — bring your own auth config, three numbered steps. - **Info callout** summarizing who needs to act. ## Editorial notes Iterated the tone a few times. Final version avoids: - Corporate "We've strengthened…" framing that made the lead redundant with the description. - A verbose change-matrix table where 3 of 4 cells said "unchanged." - Preamble-heavy migration section (e.g. *"A small number of workflows — typically those that call provider APIs…"*). - Performative support-CTA closers. Matches the voice of `12-10-25-masking.mdx`, `02-12-26-twitter-managed-credentials-removal.mdx`, and `04-07-26-bearer-token-patch.mdx` — direct, technical, non-alarming. # How did I test this PR - Reviewed format against existing security/behavior-change entries in `docs/content/changelog/` for frontmatter, heading hierarchy, code-block style, and Callout usage. - Filename follows the repo's `MM-DD-YY-slug.mdx` convention with today's date. - All API reference links verified against the current public docs.
No changes.