The Red Hat Ecosystem Catalog is the official source for discovering and learning more about the Red Hat Ecosystem of both Red Hat and certified third-party products and services.
We’re the world’s leading provider of enterprise open source solutions—including Linux, cloud, container, and Kubernetes. We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.
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.
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
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
8082/tcpThe FDO Rendezvous server listens on this port by default.
https://github.com/fedora-iot/fido-device-onboard-rs/blob/main/HOWTO.md
The following information was extracted from the dockerfile and other sources.
| Canonical image ID | FDO Rendezvous Server |
| Summary | FDO Rendezvous Server implementation |
| Description | The FDO Rendezvous server receives an Ownership Voucher from the Manufacturing server which is used for device authentication and points to the Owner Onboarding server for onboarding. |
| Provider | Red Hat |
| Maintainer | Red Hat, Inc. |
| Repository name | rhel9/fdo-rendezvous-server |
| Image version | 9.7 |
| Architecture | amd64 |
| Exposed ports | 8082:fdo-rendezvous-server |
Use a registry service account token to authenticate your container client. This allows you to pull images without using your personal Red Hat credentials, which is recommended for CI/CD pipelines and automated deployments.
Run the following command, then enter your registry token credentials when prompted by the terminal.
Pull the image
Use the following instructions to get images from a Red Hat container registry using your Red Hat login.
Run the following command, then enter your login credentials when prompted by the terminal.
Pull the image
Use the following instructions to get images from a Red Hat container registry without providing authentication.
Use the following command(s) from a system with podman installed.
Source code is available for all Red Hat UBI-based images in the form of downloadable containers. Here are a few things you should know about Red Hat source containers.
Use skopeo to copy the source image to a local directory
Inspect the image
Untar the contents
Begin examining and using the content.