@devries-cameron20 / composio Mirror · read-only / commits / 32bd1c65b
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, 22:15 UTC

docs: SEC-339 callouts on canonical authenticating-tools / connected-accounts pages

- authenticating-tools.mdx: add a warn callout to the OAuth Connections subsection pinning the cutover dates and routing readers to link(). - connected-accounts.mdx: strengthen the multi-account info callout into a warn callout naming the dates and the migration target. - custom-auth-configs.mdx: add a clarification note that the initiate() example shown there is unaffected (custom auth configs are exempt). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Composio committed Apr 25, 2026 at 18:12 UTC 32bd1c65b5bf92ffffaa1f3c7ffadf1c79c7631c
3 files changed +14 -2
docs/content/docs/auth-configuration/connected-accounts.mdx
+4 -2
@@ -259,8 +259,10 @@ Disabling masking exposes full credentials in API responses. Only disable this i
259
260 Users can connect multiple accounts for the same toolkit (e.g., personal and work Gmail).
261
262 -<Callout type="info">
263 -Use `link()` for creating accounts, as it provides hosted authentication and allows multiple accounts by default. See [Connect Link authentication](/docs/tools-direct/authenticating-tools#hosted-authentication-connect-link).
262 +<Callout type="warn">
263 +**For Composio-managed OAuth, prefer `link()`.** The `initiate()` examples below will stop working for Composio-managed OAuth auth configs starting **2026-05-08** (new orgs) / **2026-07-03** (all orgs). `link()` provides hosted authentication, allows multiple accounts by default, and is unaffected by the rollout. See [Connect Link authentication](/docs/tools-direct/authenticating-tools#hosted-authentication-connect-link), the [migration guide](/docs/auth-configuration/migrating-initiate-to-link), or the [changelog entry](/docs/changelog/2026/04/24).
264 +
265 +The `initiate()` examples remain accurate for **custom auth configs** (your own OAuth app) and **non-OAuth schemes** (API key, bearer, basic) — those are unaffected.
266 </Callout>
267
268 <Tabs groupId="language" items={['Python', 'TypeScript']} persist>
docs/content/docs/auth-configuration/custom-auth-configs.mdx
+4
@@ -98,6 +98,10 @@ Once you have the OAuth credentials, you can add them to the auth config in the
98
99 This auth config is now ready to be used in your application!
100
101 +<Callout type="info">
102 +The `initiate()` example below is **safe for custom auth configs**. The `initiate()` retirement announced in the [2026-04-24 changelog](/docs/changelog/2026/04/24) only affects **Composio-managed** auth configs on OAuth1 / OAuth2 / DCR_OAUTH — not the custom OAuth app you just configured here. Custom auth configs continue to work on `initiate()` indefinitely.
103 +</Callout>
104 +
105 <Tabs groupId="language" items={['Python', 'TypeScript']} persist>
106 <Tab value="Python">
107 ```python
docs/content/docs/tools-direct/authenticating-tools.mdx
+6
@@ -183,6 +183,12 @@ https://your-app.com/callback?user_id=user_123&status=success&connected_account_
183
184 #### OAuth Connections
185
186 +<Callout type="warn">
187 +**`initiate()` is being retired for Composio-managed OAuth.** If your auth config is Composio-managed (the default — you didn't bring your own OAuth client credentials), `initiate()` will start returning `400 BadRequest` on **2026-05-08** for new organizations and **2026-07-03** for all remaining organizations. Use [Hosted Authentication (Connect Link)](#hosted-authentication-connect-link) above with `composio.connectedAccounts.link()` (TS) / `composio.connected_accounts.link()` (Python) instead — same return shape, same `redirectUrl` / `redirect_url` field, and it works for every redirectable scheme.
188 +
189 +Custom auth configs (your own OAuth app) and non-OAuth schemes (API key, bearer token, basic) continue to work on `initiate()` unchanged. See the [migration guide](/docs/auth-configuration/migrating-initiate-to-link) and the [changelog entry](/docs/changelog/2026/04/24).
190 +</Callout>
191 +
192 For OAuth flows, you'll redirect users to complete authorization. You can specify a callback URL to control where users return after authentication:
193
194 <Tabs groupId="language" items={['Python', 'TypeScript']} persist>