@devries-cameron20 / composio-1 / commits / 1f8ab7674
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.

docs(changelog): delete 'If you need raw values' section; inline the migration guidance

The section had three problems: 1. Its title promised a workaround for both halves of the PR, but only one half actually has one. For connected-account tokens the reader can switch auth configs; for auth-config secrets there is no way back — we are telling the reader to store the value themselves. Stapling those under one header misread as parallel options. 2. The connected-account migration steps (register with Google, create an auth config, create new connections) rederive guidance the linked API reference already covers, in a format that ages badly. 3. The auth-config half duplicated a sentence already present in section 2 above it. Collapse: the auth-config migration already lives in section 2. For connected-account tokens, add one inline sentence at the end of section 1 naming the specific audience (customers using Composio for OAuth only and calling the provider directly) and pointing at the custom-auth-config API reference. The numbered Google-Cloud-Console steps were instructional content that belonged in a docs guide, not a security changelog. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Anshu Garg committed Apr 22, 2026 at 12:14 UTC 1f8ab767401c07deacb38f51377714f462d2c8a5
1 file changed +2 -10
docs/content/changelog/04-21-26-composio-managed-credentials-masking.mdx
+2 -10
@@ -64,6 +64,8 @@ After:
64
65 Connections on customer-owned auth configs are unaffected — token visibility follows your existing `mask_secret_keys_in_connected_account` setting (`xxxx...` truncation when enabled, raw passthrough when disabled).
66
67 +If you were reading Composio-managed access or refresh tokens from these responses — typically because you use Composio for OAuth and then call the provider's APIs yourself — register your own OAuth application with the provider and [create a custom auth config](/reference/api-reference/auth-configs/postAuthConfigs) against those credentials. Tokens issued against an OAuth application you own belong to you and are returned in full (subject to `mask_secret_keys_in_connected_account`).
68 +
69 ### 2. Auth-config credentials
70
71 `GET /api/v3/auth_configs` and `GET /api/v3/auth_configs/{id}` no longer return sensitive credentials in a recoverable form.
@@ -93,16 +95,6 @@ Auth configs:
95 - [`GET /api/v3/auth_configs/{id}`](/reference/api-reference/auth-configs/getAuthConfigsByNanoid)
96 - [`GET /api/v3/auth_configs`](/reference/api-reference/auth-configs/getAuthConfigs)
97
96 -### If you need raw values
97 -
98 -**Connected-account tokens.** Connect through a customer-owned auth config, and optionally set `mask_secret_keys_in_connected_account: false` on your project.
99 -
100 -1. Register an OAuth application with the provider — for Gmail, start in the [Google Cloud Console](https://console.cloud.google.com/apis/credentials).
101 -2. [Create a custom auth config](/reference/api-reference/auth-configs/postAuthConfigs) using those credentials.
102 -3. Create new connections against that auth config.
103 -
104 -**Auth-config secrets** (`client_secret`, `developer_token`, etc.). Keep these alongside the code that created the auth config — for example, in your own secret manager at upload time. The auth-config GET endpoints will only return masked or redacted values going forward.
105 -
98 <Callout type="info">
99 If your integration relies on reading `access_token`, `refresh_token`, `client_secret`, or `developer_token` from Composio API responses, you will need to act. All other integrations continue to work as before.
100 </Callout>