@devries-cameron20 / composio Mirror · read-only / commits / 86c4adf4a
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, 17:15 UTC

docs(changelog): announce callback identity verification only

Drop same-browser binding and the session-fixation description from the changelog. It now announces just the opt-in callback identity verification feature, framed as a capability, with no attack detail.

Anshu Garg committed Jul 31, 2026 at 13:51 UTC 86c4adf4abf3a6c7b96152857d3eb97d4dce9339
1 file changed +9 -18
docs/content/changelog/07-30-26-oauth-connection-binding.mdx
+9 -18
@@ -1,24 +1,15 @@
1 ---
2 -title: "OAuth connection security: same-browser binding and callback identity verification"
2 +title: "Callback identity verification for OAuth connections"
3 date: "2026-07-30"
4 -description: "Two controls against OAuth session fixation: same-browser binding, automatic on Composio managed apps, and opt-in callback identity verification per project."
4 +description: "Opt-in, per-project callback identity verification: confirm the returning user before an OAuth connection activates."
5 ---
6
7 -OAuth session fixation lets someone start a connection, hand the authorization URL to another person,
8 -and capture whatever that person connects. Composio now ships two controls against it. Same-browser
9 -binding is automatic on Composio managed apps: a connection has to be finished in the browser that
10 -started it. Callback identity verification is opt-in per project, and it's the one to reach for on
11 -your own OAuth apps, since it ties activation to your signed-in user rather than the browser.
7 +You can now add an identity check to your OAuth connections. Set a verifier URL on your project, and
8 +Composio hands each OAuth return to your server, activating the connection only after your server
9 +confirms the signed-in user is the one it was created for.
10
13 -### What shipped
11 +It is opt-in per project and, once set, covers every OAuth connection in the project. Because it
12 +confirms the returning user, it holds however the user comes back from the provider. Turn it on in
13 +Settings → General.
14
15 -- **Same-browser binding**, for Composio managed apps (default auth configs). Composio owns the OAuth
16 - app here, so it enforces this for you: a Connect Link has to be completed in the browser that
17 - started it, and a callback from a different browser is rejected. It stays on for every managed
18 - connection, including ones where identity verification is also on. Nothing to set up.
19 - [Learn more](/reference/api-reference/connected-accounts#same-browser-binding)
20 -- **Callback identity verification**, an opt-in check you turn on per project. Set a verifier URL, and
21 - Composio holds every OAuth connection in the project, managed and custom, until your server confirms
22 - the returning user matches the one it was created for. It verifies the user rather than the browser,
23 - so none of the same-browser edge cases apply. Turn it on in Settings → General.
24 - [Learn more](/reference/api-reference/connected-accounts#callback-identity-verification)
15 +[Learn more](/reference/api-reference/connected-accounts#callback-identity-verification)