---
title: "CIBA Trade-offs: Approve on a Second Device, Not the One in Use"
description: "CIBA moves authentication off the device in use: the client sends a back-channel request and the user approves on an enrolled phone. See what that buys and what it costs."
---

# CIBA Trade-offs: Approve on a Second Device, Not the One in Use

**Type:** [Trade-offs](https://yomu.fyi/visual-explainers/category/trade-offs.md)

![Trade-off diagram for CIBA: a left-to-right flow from client app to auth provider to enrolled phone, plus three panels labelled Benefit, Cost, and Condition, with a decision rule at the bottom.](https://yomufyi.s3.us-east-1.amazonaws.com/visual-explainers/d23dd010-2000-47e2-96a1-d22e83f304b9/image-f3fcac05-4e00-4137-b0e7-999982dd10f9.webp)

> CIBA moves authentication off the device in use: the client sends a back-channel request and the user approves on an enrolled phone. See what that buys and what it costs.

## Explanation

CIBA (Client-Initiated Backchannel Authentication) decouples authentication from the application: the client sends a back-channel request to an OAuth 2.0 / OpenID Connect provider, and the user approves it on a separately enrolled phone or smartwatch. The flow returns a narrowly scoped token, so an expense agent can record a decision with an approve:expenses scope instead of borrowing a broad session. The trade-off is real: you gain least-privilege approval cryptographically bound to the approver's identity, but you add a second device, polling latency, and a new MFA-fatigue surface. Use it when the device in use cannot run an interactive login, and not for same-device flows.

## FAQ

### When should I use CIBA instead of the device code flow?

CIBA fits when the consumption device cannot run an interactive login, such as a POS terminal, kiosk, or a support agent working from a phone call, and the user has a separately enrolled device to approve on. Device code flow is the safer choice when the same device can display a code and complete the flow. CIBA should not be used for same-device flows.

### Why does a CIBA push include a binding message?

The binding message describes the specific request, such as expense ID, amount, and vendor, so the approver can decide from a lock screen without opening the app. It ties the consent to one transaction rather than a blind prompt, and downstream services can verify the resulting decision. Without it, the approval carries no context.

### What is the main risk of a CIBA approval flow?

The dominant risk is MFA-fatigue-style attacks, where repeated approval pushes wear the user down until they accept one. Rate limits, short expiries, and clear binding messages reduce that exposure. Also plan for latency: poll mode adds round trips, while ping and push modes deliver tokens faster.

**Tags:** [CIBA](https://yomu.fyi/topic/ciba.md), [Human-in-the-Loop](https://yomu.fyi/topic/human-in-the-loop.md), [MFA](https://yomu.fyi/topic/mfa.md), [OAuth](https://yomu.fyi/topic/oauth.md), [OIDC](https://yomu.fyi/topic/oidc.md), [Security](https://yomu.fyi/topic/security.md)

## Related reading

### [Slack Bots on Sprites: OAuth is Easy Now](https://yomu.fyi/post/slack-bots-on-sprites-oauth-is-easy-now.md)
- Company: [Fly.io](https://yomu.fyi/company/fly-io.md)
- Published: Nov 6, 2026
- Type: Tutorial

Building a Slack bot with OAuth usually requires setting up a server with a public URL, handling callbacks, storing tokens, and maintaining them across restarts. Sprites simplifies this by providing an internet-accessible environment with a persistent filesystem, eliminating the need for Ngrok or separate hosting. To create the bot, users initialize npm, install @slack/bolt and express, and build an OAuth handler for Slack’s callback that stores tokens to the filesystem. The bot is registered as a Sprite service with sprite-env services create , which enables auto-start on HTTP requests, automatic request routing to port 8080, and persistent registration across hibernations. When idle, the Sprite hibernates to save costs and wakes in under a second, and users can create a checkpoint snapshot for easy restoration.


### [Closing the Loop: The Missing Ingredient in Agentic Development](https://yomu.fyi/post/closing-the-loop-the-missing-ingredient-in-agentic-development.md)
- Company: [Fly.io](https://yomu.fyi/company/fly-io.md)
- Published: Nov 6, 2026
- Type: Problem & solution

AI code agents that require constant permission prompts create a new form of friction similar to old copy-paste workflows. The Sprite environment solves this by giving agents unrestricted access to a fully isolated computer where they can install dependencies, start servers, and test endpoints without human intervention. Preinstalled tools such as test runners, service logs at known paths, and checkpoint-based rollback enable agents to write code, run it, observe failures, and fix issues autonomously. Additional tools like curl, jq, sqlite3, and network debugging utilities support API testing, database inspection, and network troubleshooting. The result is a tight closed loop where the agent can build, test, and ship without prompting the developer, turning the developer into the idea person rather than middleware.


### [Make Computers Make Computers](https://yomu.fyi/post/make-computers-make-computers.md)
- Company: [Fly.io](https://yomu.fyi/company/fly-io.md)
- Published: Nov 6, 2026
- Type: Explainer

Sprites are isolated virtual computers that can create and manage other Sprites via an API, and Claude can use that API when authorized by a token from sprites.dev/account. This enables automated workflows like central OAuth token management, where an Auth Sprite handles token refresh and storage for other Sprites. For CI, an orchestrator Sprite spins up a worker for each test file, locks its network to only pypi and github, runs the test, collects results, and destroys the worker. Preview environments are created per pull request, with each PR getting its own Sprite that is redeployed on updates and destroyed on merge. Additional use cases include agent delegation with network-policy-locked workers, running untrusted code in a deny-all network Sprite, and team provisioning via a provisioner Sprite that creates and configures new Sprites with checkpoints enabling fast restoration.


### [Building Secure AI Agents with Microsoft Agent Framework and Auth0: Human-in-the-Loop Approval](https://yomu.fyi/post/building-secure-ai-agents-with-microsoft-agent-framework-and-auth0-hum.md)
- Company: [Auth0](https://yomu.fyi/company/auth0.md)
- Author: Andrea Chiarelli
- Published: Sep 21, 2026
- Type: Tutorial

The post details how to add secure human-in-the-loop approval to an AI expense agent built with Microsoft Agent Framework and Auth0, completing the four-part series that handles identity, authorization, and action. Because approval is a security-sensitive action requiring the same cryptographic rigor as any authentication event, the agent uses Client-Initiated Backchannel Authentication (CIBA) to push a notification to the manager’s phone instead of accepting chat input. The notification includes a binding message describing the expense by ID, amount, vendor, and context, giving the manager enough information to decide from a lock screen. The agent polls Auth0’s token endpoint until the manager approves or denies, then uses the CIBA-issued access token scoped with approve:expenses to record the decision on a separate Expense API. This design ensures approval decisions are cryptographically bound to the manager’s identity and verifiable by downstream services, completing the secure loop.


### [Introducing CIBA for Secure Transaction Verification](https://yomu.fyi/post/introducing-ciba-for-secure-transaction-verification.md)
- Company: [Okta](https://yomu.fyi/company/okta.md)
- Author: Indranil Jha
- Published: Jul 31, 2025
- Type: Explainer

CIBA addresses identity verification when an application cannot use an interactive login on the consumption device, including bank customer-service changes, retail POS payments, browser-constrained devices, and shared kiosks. Client-Initiated Backchannel Authentication decouples authentication from the application: a client sends a back-channel request to an OAuth 2.0 authorization provider, while the user approves it on a separately enrolled phone or smartwatch. CIBA extends OpenID Connect with a grant type, discovery metadata, and poll, ping, and push token-delivery modes; in the described banking flow, the application receives a user-scoped token to update the email address. The approach improves least-privilege access and avoids exposing credentials on shared devices, but can enable MFA-fatigue-style attacks, should not be used same-device, and may warrant device code flow in some cases.
