Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
TypeScript agentic-aiagentsaiai-agentsaiagentsdeveloper-toolsfunction-callinggpt-4javascriptjsllmllmopsmcppythonremote-mcp-serverssetypescript
docs(changelog): tighten auth-config section
Anshu Garg0dcc0373b279
diff --git a/docs/content/changelog/04-21-26-composio-managed-credentials-masking.mdx b/docs/content/changelog/04-21-26-composio-managed-credentials-masking.mdxindex d2175a00f..f5d8e25fc 100644--- a/docs/content/changelog/04-21-26-composio-managed-credentials-masking.mdx+++ b/docs/content/changelog/04-21-26-composio-managed-credentials-masking.mdx@@ -66,26 +66,12 @@ Connections on customer-owned auth configs are unaffected — token visibility f### 2. Auth-config credentials-`GET /api/v3/auth_configs` and `GET /api/v3/auth_configs/{id}` now redact or mask every sensitive credential field.+`GET /api/v3/auth_configs` and `GET /api/v3/auth_configs/{id}` no longer return sensitive credentials in a recoverable form.-**Composio-managed auth configs** — every field below is replaced with `"REDACTED"`:+- **Composio-managed auth configs** — every credential field is redacted.+- **Customer-owned auth configs** — public OAuth identifiers (`client_id`, `consumer_key`) still pass through so you can debug OAuth flows. Every other credential field is obfuscated.-- `client_id`, `client_secret`, `consumer_key`, `consumer_secret`, `code_verifier`-- `bot_token`, `bearer_token`, `verification_token`, `generic_id`, `developer_token`--**Customer-owned auth configs** — `client_id` and `consumer_key` still pass through in full (you own them and need them to debug OAuth flows). The following fields are now masked as `<first-4>...<last-4>`:--- `client_secret`, `consumer_secret`, `code_verifier`-- `bot_token`, `bearer_token`, `verification_token`, `generic_id`, `developer_token`--Values shorter than 8 characters collapse to `"REDACTED"` to avoid partial leaks.--**Previously returned in plaintext:**--- `client_secret` on customer-owned auth configs.-- `developer_token` (Google Ads) and other default-scheme fields (`bot_token`, `bearer_token`, `verification_token`, `generic_id`) on Composio-managed auth configs.--If you were reading these values out of the GET response, switch to storing them alongside the code that uploaded them (see the migration section below).+If your code reads a secret — for example `client_secret` or `developer_token` — out of these responses, you will need to keep that value alongside the code that created the auth config (typically in your own secret manager at upload time). These fields were returned in plaintext under some paths on master and are now obfuscated.### Why this change