Skip to content

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): fold SEC-332 auth-config redaction into the same entry

Anshu Garg169e3a516b56
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.mdx
index fa6334ba6..4b9659750 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
@@ -1,27 +1,51 @@
---
-title: "Automatic Credential Masking for Composio-Managed Connections"
-description: "Access and refresh tokens for connections on Composio-managed auth configs are now always masked in API responses, regardless of project-level masking. Connections on your own auth config are unchanged."
+title: "Automatic Credential Masking for Composio-Managed Auth Configs and Connections"
+description: "Auth-config and connected-account API responses now redact credentials for Composio-managed resources and mask them for customer-owned ones — a fail-closed allowlist replaces the previous blacklist for both."
date: "2026-04-21"
---
-For connections created through a Composio-managed auth config, access tokens, refresh tokens, and the `Authorization` header are now always masked in `connected-accounts` API responses — regardless of your project's `mask_secret_keys_in_connected_account` setting.
+Two API surfaces now fail closed when returning credential-bearing fields, replacing two previously independent blacklists with a single allowlist policy:
+
+- **`auth_configs` GET responses** — `client_secret`, `consumer_secret`, `bot_token`, `bearer_token`, `verification_token`, `developer_token`, and any future sensitive field are hidden. Composio-managed configs return `REDACTED`; configs you own return `<first4>...<last4>`.
+- **`connected_accounts` GET / list / create responses** — `access_token`, `refresh_token`, `id_token`, and the `Authorization` header are hidden for connections on Composio-managed auth configs, regardless of your project's `mask_secret_keys_in_connected_account` setting.
**Most integrations need no changes.**
- Tool execution through the SDK, Tool Router, and MCP is unchanged. Composio handles authentication server-side, so your agents never needed to read these tokens directly.
-- Connections on your own auth config are unchanged. Token visibility continues to follow your project's masking setting.
+- Connections and auth configs that you own still return your credentials — masked when your project has masking enabled, raw when it doesn't.
### What is a Composio-managed auth config?
-When you connect a user through a toolkit's default integration — for example, Gmail or Slack without registering your own OAuth application — the connection runs through an OAuth application that Composio owns and operates on behalf of every team using that default. The access and refresh tokens the provider issues are bound to Composio's shared OAuth client.
+When you connect a user through a toolkit's default integration — for example, Gmail or Slack without registering your own OAuth application — the connection runs through an OAuth application that Composio owns and operates on behalf of every team using that default. The `client_secret` of that application, and the access and refresh tokens the provider issues for connections on it, are bound to Composio's shared OAuth client.
-You can identify a Composio-managed connection by the `auth_config.is_composio_managed: true` field on the connected-account resource.
+You can identify a Composio-managed auth config or connection by the `is_composio_managed: true` field on the resource.
### Why this change
-A single OAuth application backs every team on a default integration, and the tokens we return are bound to it. If a provider throttles, restricts, or suspends that app in response to misuse of one of its tokens, the integration becomes unavailable for every team on the default at once. Masking the tokens keeps that exposure out of API responses; Composio still uses them server-side, so tool execution is unchanged.
+A single OAuth application backs every team on a default integration, and the credentials we return — both the `client_secret` on the auth config and the tokens on connections made through it — are bound to that one application. If a provider throttles, restricts, or suspends the app in response to misuse of one of its credentials, the integration becomes unavailable for every team on the default at once.
+
+Under the previous blacklist design, every new field added to a default auth scheme shipped raw until someone remembered to add it to the mask list. The most recent example was the Google Ads `developer_token`. The allowlist flips this: new fields are masked by default, and classifying a field as safe requires an explicit code change.
+
+### Auth configs — what changed in responses
+
+For `GET /api/v3/auth_configs` and `GET /api/v3/auth_configs/{id}`, the `credentials` object now behaves like this:
+
+| Field | Custom auth config (`is_composio_managed: false`) | Composio-managed (`is_composio_managed: true`) |
+|---|---|---|
+| `scopes`, `user_scopes`, `scope`, `user_scope` | Pass through | Pass through |
+| `oauth_redirect_uri`, `token_url`, `base_url` | Pass through | Pass through |
+| `permissions`, `user_agent`, `client_name`, `logo_uri` | Pass through | Pass through |
+| `full`, `region`, `subdomain`, `shop`, `hostUrl`, `version`, `prefix`, `suffix` | Pass through | Pass through |
+| `client_id`, `consumer_key` | Pass through (you own it) | `REDACTED` (Composio owns it) |
+| `client_secret`, `consumer_secret`, `code_verifier` | `<first4>...<last4>` | `REDACTED` |
+| `bot_token`, `bearer_token`, `verification_token`, `generic_id`, `developer_token` | `<first4>...<last4>` | `REDACTED` |
+| Any future unlisted field | `<first4>...<last4>` | `REDACTED` |
-### Example
+Strings shorter than 8 characters fall back to `REDACTED` instead of partial disclosure.
+
+### Connected accounts — what changed in responses
+
+For `GET /api/v3/connected_accounts`, `GET /api/v3/connected_accounts/{id}`, and `POST /api/v3/connected_accounts`, the `state.val`, `data`, `params`, and `headers.Authorization` fields are now always masked for connections on Composio-managed auth configs — regardless of your project's `mask_secret_keys_in_connected_account` setting.
Before, with project masking disabled on a Composio-managed Gmail connection:
@@ -49,17 +73,24 @@ After:
}
```
-The same applies to `data`, `params`, and `headers.Authorization` wherever these values would otherwise appear.
+Connections on auth configs you own continue to follow your project's masking setting as before — raw tokens when masking is off, truncated when it's on.
### Affected endpoints
+Auth configs:
+
+- [`GET /api/v3/auth_configs`](/reference/api-reference/auth-configs/getAuthConfigs)
+- [`GET /api/v3/auth_configs/{id}`](/reference/api-reference/auth-configs/getAuthConfigsByNanoid)
+
+Connected accounts:
+
- [`GET /api/v3/connected_accounts/{id}`](/reference/api-reference/connected-accounts/getConnectedAccountsByNanoid)
- [`GET /api/v3/connected_accounts`](/reference/api-reference/connected-accounts/getConnectedAccounts)
- [`POST /api/v3/connected_accounts`](/reference/api-reference/connected-accounts/postConnectedAccounts)
-### If you need raw tokens
+### If you need raw credentials
-To keep reading `access_token` or `refresh_token` from API responses, connect through your own auth config. Tokens issued against an OAuth application you own are returned in full (subject to your project's masking setting).
+If your workflow reads `client_secret` from an auth-config response, or `access_token` / `refresh_token` from a connected-account response, own the auth config yourself. Secrets on your own OAuth application are returned in full (subject to your project's masking setting).
1. Register an OAuth application with the provider — for Gmail, start in the [Google Cloud Console](https://console.cloud.google.com/apis/credentials).
2. [Create a custom auth config](/reference/api-reference/auth-configs/postAuthConfigs) using those credentials.