V1
CIBA
OpenID Connect Client-Initiated Backchannel Authentication Flow
Parameters
| Name | In | Type | Required | Description |
|---|---|---|---|---|
| body | body | object | false | ‘none’ |
Request body - Content-Type: application/x-www-form-urlencoded
Custom schema example
|
|
| Name | Type | Required | Description |
|---|---|---|---|
| login_hint | string | true | A hint to the OpenID Provider regarding the end-user for whom authentication is being requested. The value may contain an email address or msisdn, which identifies the end-user to the OP |
| scope | string | false | Scope of permissions |
| binding_message | string | false | A human-readable identifier or message intended to be displayed on both the consumption device and the authentication device to interlock them together for the transaction by way of a visual cue for the end-user. This interlocking message enables the end-user to ensure that the action taken on the authentication device is related to the request initiated by the consumption device. |
Request example
|
|
Responses
| Code | Meaning | Description | Schema |
|---|---|---|---|
| 200 | OK | OK | bcAuthorizeResponse |
| 400 | Bad Request | Bad Request | errorAccessTokenResponse |
| 401 | Unauthorized | Unauthorized | errorAccessTokenResponse |
Endpoints
TokenInfo
OAuth2
Magic Links
CIBA
WebAuthn
Device Code