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): drop allowlist/blacklist implementation jargon
Anshu Garg87bdf2719393
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 4b9659750..31ecbe389 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,12 +1,12 @@---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."+description: "Auth-config and connected-account API responses now redact credentials for Composio-managed resources. Credentials for resources you own continue to behave as before, masked according to your project's masking setting."date: "2026-04-21"----Two API surfaces now fail closed when returning credential-bearing fields, replacing two previously independent blacklists with a single allowlist policy:+Two API surfaces now hide credential-bearing fields more strictly in responses:-- **`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>`.+- **`auth_configs` GET responses** — `client_secret`, `consumer_secret`, `bot_token`, `bearer_token`, `verification_token`, `developer_token`, and any other sensitive field are hidden. Composio-managed configs return `REDACTED`; configs you own return a masked form (`<first4>...<last4>`) so you can still recognize the value you uploaded.- **`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.**@@ -24,7 +24,7 @@ You can identify a Composio-managed auth config or connection by the `is_composiA 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.+Hiding these values at the API boundary keeps that risk contained while tool execution continues to work unchanged — Composio uses the credentials server-side.### Auth configs — what changed in responses