Specify a Connection when Using Device Authorization Flow

Last Updated: Aug 14, 2024

Overview

When using a CLI application with the Device Authorization Flow, a single Social Connection has been defined. The intention is to pass the connection_id as a login query parameter to allow the user to log straight into the application, bypassing the Auth0 login screen. This implementation does not work.

Applies To

  • CLI Application
  • connection_id
  • Device Authorization Flow

Solution

The RFC 8628 defines the standards for the OAuth 2.0 Device Authorization Grant. This document does not specify the ability to pass a Connection parameter as an option. Auth0 complies with the Standard and does not support the requested capability.

Calls to the POST /oauth/device/code endpoint only support the following parameters:

  • audience: The unique identifier of the target API.
  • scope: The scopes to request authorization for.
  • client_id: The application’s ID.

Related References