@devries-cameron20 / composio-1 / commits / 952d64469
Fork 0

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

docs(changelog): drop 'previously plaintext' self-confession from lead + description

Same reasoning as the prior commit — a security changelog should state the current contract and the required action, not publicly catalog which specific paths used to leak. The description and the second lead bullet carried the same self-annotation as the auth-config migration sentence; removing it for consistency. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Anshu Garg committed Apr 22, 2026 at 12:22 UTC 952d64469af748854a832c94339dedfdd8b57fd4
1 file changed +2 -2
docs/content/changelog/04-22-26-composio-managed-credentials-masking.mdx
+2 -2
@@ -1,13 +1,13 @@
1 ---
2 title: "Credential Redaction for Composio-Managed Auth Configs and Connections"
3 -description: "Composio-managed auth configs and their connections now redact sensitive fields in API responses. Customer-owned auth configs continue to mask secrets; previously plaintext client_secret and developer_token values are now masked as well."
3 +description: "Composio-managed auth configs and their connections now redact sensitive fields in API responses. Customer-owned auth configs mask every credential field except the public OAuth identifiers."
4 date: "2026-04-22"
5 ---
6
7 Two related security changes are rolling out together:
8
9 1. **Connections on Composio-managed auth configs** now always redact `access_token`, `refresh_token`, and the `Authorization` header in `connected-accounts` responses — independent of your project's `mask_secret_keys_in_connected_account` flag.
10 -2. **Auth-config GET responses** now redact (for Composio-managed) or mask (for customer-owned) every sensitive credential field — including `client_secret` and `developer_token`, which were previously returned in plaintext under some paths.
10 +2. **Auth-config GET responses** now redact (for Composio-managed) or mask (for customer-owned) every sensitive credential field.
11
12 Auth-config credential redaction is **not controlled by `mask_secret_keys_in_connected_account`**. That project flag only applies to runtime connected-account credentials (access tokens, refresh tokens, and the like). Auth-config credentials are developer-owned static fields — `client_id`, `client_secret`, `developer_token`, etc. — and are always redacted or masked regardless of the `mask_secret_keys_in_connected_account` project flag.
13