Components of the FDO system

FIDO Device Onboarding (FDO) onboarding employs a device-side client application and three specialized FDO servers: Manufacturing, Rendezvous, and Owner.

Device client

This application is installed on the device and performs the following operations:

  • During device manufacture, the client application initializes the device’s FDO state with the help of the Manufacturing server.
  • When the final owner installs the device, the client application performs the onboarding process in concert with the Rendezvous and Owner FDO servers.
Manufacturing server
Deployed at the device manufacturer’s site, this server is responsible for the FDO Device Initialization protocol, which prepares the device for the FDO onboarding process and creates the Ownership Voucher. The device client initiates device initialization. Once device initialization completes, the Manufacturing server has no further involvement with the onboarding process.
Rendezvous server
To enable late binding of device ownership, which is required when the device’s ownership is unknown during manufacturing, the device requires a discovery service at the start of onboarding to securely identify its owner. The Rendezvous server provides this discovery service. The device client contacts the Rendezvous server at the start of the onboarding process to retrieve the network addresses for the Owner server.
Owner server
The device owner’s organization deploys the Owner server. It is responsible for integrating the new device into the owner’s IoT infrastructure. When the device is installed and first booted at the owner’s facility, the device client connects to the Owner server and initiates the final phase of onboarding. The FDO onboarding process completes once the Owner server finishes provisioning the device for use.