Description

FDO Rendezvous Server container

The FDO Rendezvous server is the first point of contact for a newly powered on Edge device during Onboarding. The FDO Rendezvous server receives an Owner Voucher from the Manufacturing server which is used for device authentication and points to the Owner Onboarding server for onboarding automation.

Generate the needed certificates and keys

Install the fdo-admin-cli tool by running the following command:

dnf install fdo-admin-cli

To generate the needed certificates and keys:

 mkdir keys
 for i in "diun" "manufacturer" "device-ca" "owner"; do fdo-admin-tool generate-key-and-cert $i; done

This will populate the 'keys' directory with all the certificates and keys needed to use the various FDO containers. Below is a list of which containers will need which certificates and keys.

fdo-manufacturing-server: diun_key.der, diun_cert.pem, manufacturer_cert.pem, manufacturer_cert.der, owner_cert.pem, device_ca_key.der, device_ca_cert.pem

fdo-rendezvous-server: manufacturer_cert.pem

fdo-owner-onboarding-server: device_ca_cert.pem, owner_key.der, owner_cert.pem

fdo-serviceinfo-api-server: None

Usage with Podman

Edit the example configuration file to adjust the paths used on the local system.

podman run -d \
    --name fdo-rendezvous-server \
    -p 8082:8082 \
    -v /local/path/to/keys/:/etc/fdo/keys:Z \
    -v /local/path/to/config:/etc/fdo/rendezvous-server.conf.d/:Z \
    registry.redhat.io/rhel9/fdo-rendezvous-server

Ports

8082/tcp

The FDO Rendezvous server listens on this port by default.

Additional Usage Documentation

https://github.com/fedora-iot/fido-device-onboard-rs/blob/main/HOWTO.md

Upstream Documentation

https://fidoalliance.org/specs/FDO/FIDO-Device-Onboard-RD-v1.1-20211214/FIDO-device-onboard-spec-v1.1-rd-20211214.html