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): drop 'previously plaintext' self-confession from lead + description

Anshu Garg952d64469af7
diff --git a/docs/content/changelog/04-22-26-composio-managed-credentials-masking.mdx b/docs/content/changelog/04-22-26-composio-managed-credentials-masking.mdx
index 811a959f8..f492cf564 100644
--- a/docs/content/changelog/04-22-26-composio-managed-credentials-masking.mdx
+++ b/docs/content/changelog/04-22-26-composio-managed-credentials-masking.mdx
@@ -1,13 +1,13 @@
---
title: "Credential Redaction for Composio-Managed Auth Configs and Connections"
-description: "Composio-managed auth configs and their connections now redact sensitive fields in API responses. Customer-owned auth configs continue to mask secrets; previously plaintext client_secret and developer_token values are now masked as well."
+description: "Composio-managed auth configs and their connections now redact sensitive fields in API responses. Customer-owned auth configs mask every credential field except the public OAuth identifiers."
date: "2026-04-22"
---
Two related security changes are rolling out together:
1. **Connections on Composio-managed auth configs** now always redact `access_token`, `refresh_token`, and the `Authorization` header in `connected-accounts` responses — independent of your project's `mask_secret_keys_in_connected_account` flag.
-2. **Auth-config GET responses** now redact (for Composio-managed) or mask (for customer-owned) every sensitive credential field — including `client_secret` and `developer_token`, which were previously returned in plaintext under some paths.
+2. **Auth-config GET responses** now redact (for Composio-managed) or mask (for customer-owned) every sensitive credential field.
Auth-config credential redaction is **not controlled by `mask_secret_keys_in_connected_account`**. That project flag only applies to runtime connected-account credentials (access tokens, refresh tokens, and the like). Auth-config credentials are developer-owned static fields — `client_id`, `client_secret`, `developer_token`, etc. — and are always redacted or masked regardless of the `mask_secret_keys_in_connected_account` project flag.