What is CIBA?
Client-Initiated Backchannel Authentication (OpenID CIBA) lets a client start authentication without a browser redirect. The OP authenticates the user on a separate device/app, then the client obtains tokens via Poll, Ping, or Push delivery.
This workbench runs live /bc-authorize and token grants against your OP (browser-direct or stbox proxy), auto-polls on an interval, and captures Ping/Push callbacks on an ephemeral webhook inbox — without uploading secrets to stbox.
How to use this tool
- Choose Poll, Ping, or Push; fill scope, client auth, and a user hint; register delivery mode and (for Ping/Push) client_notification_endpoint at the OP.
- Submit /bc-authorize. For Poll, open Delivery → Start polling. For Ping/Push, create the notification inbox and wait for SSE events (Ping auto-calls /token).
- Use Build snippets (curl/fetch/Node) when integrating your own client. The local poll sim is reference-only.
Frequently asked questions
Does stbox call my OpenID Provider?
When you click Submit or Start polling, yes — via browser-direct or the stbox HTTP proxy. Ping/Push use a temporary webhook inbox so the OP can POST notifications to this host.
Are notification inboxes durable?
No. Hooks are in-memory and reset on server restart. The OP must be able to reach your stbox URL (local or deployed). Use them for integration testing, not production callbacks.
What is the CIBA grant type?
urn:openid:params:grant-type:ciba — used at the token endpoint with auth_req_id after a successful backchannel authentication request.