Device authorization grant
The OAuth 2.0 Device Authorization Grant, defined by RFC 8628, lets customers authorize applications running on internet-connected devices that have limited input capabilities or no suitable browser.
Typical use cases include smart TVs, game consoles, kiosks, and similar devices. The customer completes authentication on a separate device, such as a phone or computer. After authorization is complete, the original device can obtain tokens for the customer.
For protocol-level requirements and request and response parameters, see RFC 8628.
Configure the client
Enable the Device Authorization Grant for the OAuth2/OIDC client that will use the flow:
- Go to Applications and open the application you want to use for device authorization.
- Select the Clients tab and open an OAuth2/OIDC client.
- On the Application URLs tab, set the Customer-friendly login page URL. The configured value appears in the verification URL.
- Select the OAuth2/OIDC tab. Under Advanced, toggle Enable device authorization grant.
See OAuth2/OIDC properties setup for detailed client configuration.
The device code and user code expire after five minutes.
Integrate a device application
The device application communicates directly with Strivacity to initiate the authorization request and retrieve tokens.
Use the device_authorization_endpoint from your instance's /.well-known/openid-configuration document to initiate the Device Authorization Grant.
The device application:
- Sends a device authorization request to Strivacity.
- Receives a device code, user code, verification URI, and complete verification URI.
- Presents the verification URI and user code to the customer. The complete verification URI can also be represented as a QR code.
- Polls the token endpoint using the device code while the customer completes authorization on another device.
- Continues polling while authorization is pending.
- Receives an access token after the customer successfully completes authorization. If refresh tokens are enabled and the offline scope was requested, Strivacity also returns a refresh token.
For the request and response formats, polling requirements, and error responses, see RFC 8628.
Customer authorization flow
After the device initiates the request:
- The customer opens the verification URI on another device, such as a phone or computer.
- If the user code is not already included in the URI, the customer enters the code displayed by the original device.
- The customer signs in to their account.
- After successful authentication, Strivacity displays a confirmation that the device is connected.
- The device can use the issued access token to access the authorized resources.
The device is then listed under Authorized devices in the Security settings section of the My Account portal. Customers can remove authorized devices from their account.
Updated about 6 hours ago

