Approving a sign-on request (companion app)

Request

When the user enters the device registration code on the app on the companion device, the companion app should approve the request with DSRA. To do this, it should send a PUT request to:

https://<host>:<port>/dsra/v1/user/deviceRegistrationCode/actions/approve

Headers

• x-correlation-id – identifier for logging, to correlate messages across a call flow

• Authorization – the device’s OPF access token (which it received when it signed on or refreshed its access token). Must be preceded by Bearer (note the space).

Mandatory arguments

• deviceRegistrationCode – the device registration code entered by the user

Other arguments

None

Response

A successful response returns an HTTP 202 status.

A bad request returns an HTTP 400 status. This happens if the request is invalid, or if the token or payload is missing or incomplete.

If the token is invalid or if there is an issue with the device registration code (expired, invalid, already approved, or already registered), the service returns an HTTP 403 status.

If the device registration code is not recognised (for example, if the user typed it incorrectly), the service returns an HTTP 404 status.

See also

Device SignOn and Registration Assistant (DSRA) API documentation