1
---
2
title: "OAuth connection security: same-browser binding and callback identity verification"
3
date: "2026-07-30"
4
-description: "Stop an OAuth connection from being completed by another party: same-browser binding on Composio-managed apps, and opt-in, per-project callback identity verification."
4
+description: "Stop an OAuth connection from being completed by another party: same-browser binding on Composio managed apps, and opt-in, per-project callback identity verification."
5
---
6
7
-Composio now stops an OAuth connection from being completed by someone other than the person who
8
-started it. On Composio-managed apps this is enforced automatically, bound to the browser that
9
-started the flow. Any project can also opt into callback identity verification, which ties activation
10
-to the user — the durable way to secure your own OAuth apps.
7
+Composio now stops an OAuth connection from being completed by anyone other than the person who
8
+started it. On Composio managed apps this is automatic: the connection is bound to the browser that
9
+began it. And any project can turn on callback identity verification, which ties activation to your
10
+signed-in user. That's the one to reach for on your own OAuth apps, since it checks the user rather
11
+than the browser.
12
13
### What shipped
14
14
-- **Same-browser binding** — for **Composio-managed apps** (default auth configs). Because Composio
15
- owns the OAuth app here, it enforces this automatically: a Connect Link must be completed in the
16
- browser that started it, and a callback from a different browser is rejected. It stays on for every
17
- managed connection, including where identity verification is also enabled. No setup required.
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)
19
-- **Callback identity verification** — an opt-in, per-project identity check, and the most reliable
20
- way to secure your **own OAuth apps**. Set a verifier URL, and Composio holds every OAuth connection
21
- in the project — managed and custom alike — until your server confirms the returning user matches
22
- the one it was created for. Enable it in Settings → General.
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)