@devries-cameron20 / composio Mirror · read-only / commits / 0dcc0373b
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): tighten auth-config section

Three problems with the prior revision of the auth-config section: 1. Enumerated every masked field. Customers don't need the list; the rule is fail-closed (anything not client_id/consumer_key is obfuscated), and any enumeration rots when new fields ship. 2. Described the mask format (<first-4>...<last-4>, 8-char fallback). That's an internal implementation detail — useful to attackers, not actionable for customers, and brittle if we change the format. 3. Separate "previously returned in plaintext" bullet list duplicated the migration guidance without clarifying what action to take. New version states the contract in two bullets (managed = redacted, customer-owned = public IDs pass through, everything else obfuscated) and folds the plaintext-regression note into the migration sentence itself, naming only the two fields (client_secret, developer_token) that actually drive migration action. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Anshu Garg committed Apr 22, 2026 at 12:13 UTC 0dcc0373b27902cdaa689584e66db7d53d704976
1 file changed +4 -18
docs/content/changelog/04-21-26-composio-managed-credentials-masking.mdx
+4 -18
@@ -66,26 +66,12 @@ Connections on customer-owned auth configs are unaffected — token visibility f
66
67 ### 2. Auth-config credentials
68
69 -`GET /api/v3/auth_configs` and `GET /api/v3/auth_configs/{id}` now redact or mask every sensitive credential field.
69 +`GET /api/v3/auth_configs` and `GET /api/v3/auth_configs/{id}` no longer return sensitive credentials in a recoverable form.
70
71 -**Composio-managed auth configs** — every field below is replaced with `"REDACTED"`:
71 +- **Composio-managed auth configs** — every credential field is redacted.
72 +- **Customer-owned auth configs** — public OAuth identifiers (`client_id`, `consumer_key`) still pass through so you can debug OAuth flows. Every other credential field is obfuscated.
73
73 -- `client_id`, `client_secret`, `consumer_key`, `consumer_secret`, `code_verifier`
74 -- `bot_token`, `bearer_token`, `verification_token`, `generic_id`, `developer_token`
75 -
76 -**Customer-owned auth configs** — `client_id` and `consumer_key` still pass through in full (you own them and need them to debug OAuth flows). The following fields are now masked as `<first-4>...<last-4>`:
77 -
78 -- `client_secret`, `consumer_secret`, `code_verifier`
79 -- `bot_token`, `bearer_token`, `verification_token`, `generic_id`, `developer_token`
80 -
81 -Values shorter than 8 characters collapse to `"REDACTED"` to avoid partial leaks.
82 -
83 -**Previously returned in plaintext:**
84 -
85 -- `client_secret` on customer-owned auth configs.
86 -- `developer_token` (Google Ads) and other default-scheme fields (`bot_token`, `bearer_token`, `verification_token`, `generic_id`) on Composio-managed auth configs.
87 -
88 -If you were reading these values out of the GET response, switch to storing them alongside the code that uploaded them (see the migration section below).
74 +If your code reads a secret — for example `client_secret` or `developer_token` — out of these responses, you will need to keep that value alongside the code that created the auth config (typically in your own secret manager at upload time). These fields were returned in plaintext under some paths on master and are now obfuscated.
75
76 ### Why this change
77