@devries-cameron20 / composio Mirror · read-only / commits / ed3915de7
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): rewrite for customer-trust tone

Anshu Garg committed Apr 21, 2026 at 01:34 UTC ed3915de76117f80b4b909ffc59ac821013bdc07
1 file changed +32 -28
docs/content/changelog/04-21-26-composio-managed-credentials-masking.mdx
+32 -28
@@ -1,42 +1,47 @@
1 ---
2 -title: "Composio-Managed Auth Configs Always Mask Access and Refresh Tokens"
3 -description: "API responses no longer return raw access or refresh tokens for connections on Composio-managed auth configs, regardless of project masking settings. Connections on your own auth config are unchanged."
2 +title: "Automatic Credential Masking for Composio-Managed Connections"
3 +description: "We've strengthened how credentials are protected for Composio-managed auth configs. Access and refresh tokens are now always masked in API responses for these connections, keeping the shared OAuth applications that back our default integrations reliable for every team using them."
4 date: "2026-04-21"
5 ---
6
7 -Access tokens, refresh tokens, and the `Authorization` header returned by the connected-accounts API are now always masked for connections created through **Composio-managed auth configs**, regardless of the project's `mask_secret_keys_in_connected_account` setting. Connections created through your own auth config are unchanged.
7 +We've strengthened how credentials are protected on Composio-managed auth configs. For connections that use one of Composio's default toolkit integrations, access tokens, refresh tokens, and the `Authorization` header are now always masked in `connected-accounts` API responses — independent of your project's `mask_secret_keys_in_connected_account` setting.
8 +
9 +**Most integrations need no changes.**
10 +
11 +- Tool execution through the SDK, Tool Router, and MCP is unchanged. Composio continues to handle authentication server-side, so your agents and workflows never needed to read these tokens directly.
12 +- Connections on your own auth config are unchanged. Token visibility continues to follow your project's masking setting exactly as before.
13
14 ## What is a Composio-managed auth config?
15
11 -When you use a toolkit's default integration — for example, connecting a user to Gmail or Slack without registering your own OAuth application — the connection runs through an OAuth app that **Composio owns and shares across every customer on that default**. The access and refresh tokens the provider issues against that connection are bound to Composio's shared OAuth client, not to any credentials of yours.
16 +When you connect a user through a toolkit's default integration — for example, Gmail or Slack without registering your own OAuth application — the connection is authorized through an OAuth application that Composio maintains on behalf of every team using that default. The access and refresh tokens the provider issues for that connection are bound to Composio's shared OAuth client.
17
18 You can tell a connection is Composio-managed by the `auth_config.is_composio_managed: true` field on the connected-account resource.
19
15 -## Why this change
20 +## Why we're making this change
21
17 -Because the OAuth application is shared, any enforcement the provider applies to it — rate limits, scope restrictions, or app-level bans — lands on **every** customer using that default integration. A single token used in ways that violate a provider's terms of service can degrade or break the default Gmail, Slack, or any other managed integration for every other customer on it.
22 +Because the OAuth application is shared across every team on that default, any action a provider takes on it — rate limits, scope adjustments, or in the extreme case, suspending the OAuth client — is felt by everyone using it. A shared application means shared outcomes.
23
19 -Returning the raw tokens to the caller invited that risk. From now on, the connected-accounts API never exposes them. Composio continues to hold and use the tokens server-side to execute tools on your behalf.
24 +Keeping these credentials inside Composio removes an avenue of risk that no single customer can contain on their own, and lets us keep the default integrations healthy and available for every team that relies on them. Tool execution flows continue to work without any change; Composio uses the tokens server-side so your agents don't need to.
25
21 -## What's changing in the API
26 +## What changes in the API
27
23 -| Auth config | `mask_secret_keys_in_connected_account` | Tokens returned |
28 +| Connection type | Project masking setting | Tokens in response |
29 |---|---|---|
25 -| Composio-managed | on | masked (unchanged) |
26 -| Composio-managed | **off** | **masked (new)** |
27 -| Your own auth config | on | masked (unchanged) |
28 -| Your own auth config | off | raw (unchanged) |
30 +| Composio-managed | On | Masked (unchanged) |
31 +| Composio-managed | Off | **Masked (new behavior)** |
32 +| Your own auth config | On | Masked (unchanged) |
33 +| Your own auth config | Off | Returned in full (unchanged) |
34
35 ### Example
36
32 -Before (project masking off, Composio-managed Gmail connection):
37 +Before, with project masking disabled on a Composio-managed Gmail connection:
38
39 ```json
40 {
41 "state": {
42 "val": {
38 - "access_token": "ya29.a0ARrdaM9_full_secret_token",
39 - "refresh_token": "1//04_full_refresh_secret"
43 + "access_token": "ya29.a0ARrdaM9...full token...",
44 + "refresh_token": "1//04...full token..."
45 }
46 }
47 }
@@ -55,7 +60,7 @@ After:
60 }
61 ```
62
58 -The same masking is applied wherever the same values appear in the response, including the `data`, `params`, and merged `headers.Authorization` fields.
63 +The same treatment applies to the `data`, `params`, and `headers.Authorization` fields wherever these values would otherwise appear.
64
65 ### Affected endpoints
66
@@ -63,19 +68,18 @@ The same masking is applied wherever the same values appear in the response, inc
68 - [`GET /api/v3/connected_accounts`](https://docs.composio.dev/rest-api/connected-accounts/get-connected-accounts)
69 - [`POST /api/v3/connected_accounts`](https://docs.composio.dev/rest-api/connected-accounts/post-connected-accounts)
70
66 -### What's not affected
71 +## If your workflow reads tokens directly
72
68 -- **Tool execution** — `POST /api/v3/tools/execute/*`, Tool Router, and MCP continue to work. Composio uses the tokens server-side; your agents do not need to see them.
69 -- **Connections on your own auth config** — token visibility still follows your project's masking setting exactly as before.
73 +A small number of workflows — typically those that call provider APIs outside of Composio's execution path — read `access_token` or `refresh_token` from the connected-accounts response. If that's you, the recommended path is to connect through an auth config you own. Tokens issued against your OAuth application belong to you, and the connected-accounts API returns them in full (subject to your project's masking setting).
74
71 -## Need raw tokens? Bring your own auth config
75 +Getting set up:
76
73 -Tokens issued against your own OAuth application belong to you, and the connected-accounts API returns them in the clear (subject to your project's masking setting). To move a connection off the shared default:
77 +1. Register an OAuth application with the provider — for Gmail, you can start in the [Google Cloud Console](https://console.cloud.google.com/apis/credentials).
78 +2. [Create a custom auth config](https://docs.composio.dev/rest-api/auth-configs/post-auth-configs) using those credentials.
79 +3. Create new connections against that auth config. Response fields behave as they always have for customer-owned configs.
80
75 -1. Register an OAuth application with the provider (e.g., in the [Google Cloud Console](https://console.cloud.google.com/apis/credentials) for Gmail).
76 -2. [Create a custom auth config](https://docs.composio.dev/rest-api/auth-configs/post-auth-configs) with your credentials.
77 -3. Initiate new connections against that auth config.
78 -
79 -<Callout type="warn">
80 -**Action required only if you read `access_token` or `refresh_token` from the connected-accounts API for Composio-managed connections.** Existing tool-execution flows (the SDK, Tool Router, MCP) do not look at those fields and continue to work without changes. If your code path does depend on raw tokens, migrate those connections to your own auth config.
81 +<Callout type="info">
82 +**No action is needed for most teams.** If you build on the Composio SDK, Tool Router, or MCP, your integrations keep working as-is. If your application reads `access_token` or `refresh_token` directly from a Composio-managed connection, moving those connections onto a custom auth config preserves the previous response shape.
83 </Callout>
84 +
85 +Questions about migration or anything else? We're happy to help — reach out on [Slack](https://dub.composio.dev/slack) or open a thread in support and we'll walk through it with you.