@devries-cameron20 / composio Mirror · read-only / commits / 87bdf2719
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.

Mirrored from https://github.com/Camo67/composio.git

Synced Nov 21, 23:30 UTC

docs(changelog): drop allowlist/blacklist implementation jargon

Anshu Garg committed Apr 21, 2026 at 22:44 UTC 87bdf2719393f4dba982f145198e4bc870020691
1 file changed +4 -4
docs/content/changelog/04-21-26-composio-managed-credentials-masking.mdx
+4 -4
@@ -1,12 +1,12 @@
1 ---
2 title: "Automatic Credential Masking for Composio-Managed Auth Configs and Connections"
3 -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."
3 +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."
4 date: "2026-04-21"
5 ---
6
7 -Two API surfaces now fail closed when returning credential-bearing fields, replacing two previously independent blacklists with a single allowlist policy:
7 +Two API surfaces now hide credential-bearing fields more strictly in responses:
8
9 -- **`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>`.
9 +- **`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.
10 - **`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.
11
12 **Most integrations need no changes.**
@@ -24,7 +24,7 @@ You can identify a Composio-managed auth config or connection by the `is_composi
24
25 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.
26
27 -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.
27 +Hiding these values at the API boundary keeps that risk contained while tool execution continues to work unchanged — Composio uses the credentials server-side.
28
29 ### Auth configs — what changed in responses
30