Token Daisy Chain Authentication

Token Daisy Chain Authentication is a device-level verification step. It confirms that the device can correctly respond to cryptographic challenges, forming the foundation of the authentication process.

Why it matters:

1. Ensures that only genuine devices can access the system.
2. Prevents unauthorized or rogue devices from entering the network.
3. Provides a secure starting point for host verification and subsequent Secure Boot checks.

End-to-End Usage Guide

Token Daisy Chain Authentication validates a sequence of devices in a predefined order. Each device contributes to the authentication chain, ensuring that all devices are genuine and correctly linked before authentication succeeds.

Prerequisites

Before using the Daisy Chain APIs:

• Login using username and password to obtain an access token.
• Include the access token in the Authorization header for all subsequent API calls.
• Keep CF-Access-Client-ID and CF-Access-Client-Secret ready.
• Ensure you have the ordered list of device TIDs and optional intermediate data.

The flow consists of three steps:

1. Login Authorization
2. Request a Daisy Chain Challenge Word (CW)
3. Reply with the Daisy Chain Response Word (RW)
4. Check the Daisy Chain Authentication Status