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 server side implementation of the "Device Initialize" protocol, the FDO Manufacturing Server is responsible for signing a device and creating a voucher used for device ownership.
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-manufacturing-server \
-p 8080:8080 \
-v /local/path/to/keys/:/etc/fdo/keys:Z \
-v /local/path/to/config:/etc/fdo/manufacturing-server.conf.d/:Z \
-v /local/path/to/stores:/etc/fdo/stores/:Z \
registry.redhat.io/rhel9/fdo-manufacturing-server
8080/tcp
The Manufacturing server listens on this port by default.
https://github.com/fedora-iot/fido-device-onboard-rs/blob/main/HOWTO.md
The leading enterprise operating system to speed application delivery across physical, virtual, and cloud environments.
An implementation of the FIDO Device Onboard Specification written in rust.
Use the following instructions to get images from a Red Hat container registry using registry service account tokens. You will need to create a registry service account to use prior to completing any of the following tasks.
First, you will need to add a reference to the appropriate secret and repository to your Kubernetes pod configuration via an imagePullSecrets field.
Then, use the following from the command line or from the OpenShift Dashboard GUI interface.
Use the following command(s) from a system with podman installed
Use the following command(s) from a system with docker service installed and running
Use the following instructions to get images from a Red Hat container registry using your Red Hat login.
For best practices, it is recommended to use registry tokens when pulling content for OpenShift deployments.
Use the following command(s) from a system with podman installed
Use the following command(s) from a system with docker service installed and running
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.