Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs: correct note about certificate chain order #2607

Merged
merged 1 commit into from
Jan 24, 2024
Merged

docs: correct note about certificate chain order #2607

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/src/operate/security/device-certificate.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,12 +36,12 @@ Note that *only* the MQTT broker should be able to read or write the private key
Then thin-edge must be told where the certificate is stored.
Note that the device certificate file must contain not only the device certificate itself
but also the signing certificate
(so the cloud endpoint can check the chain, starting from a trusted root upto the device certificate).
(so the cloud endpoint can check the chain, starting from the device certificate up to the trusted root).

```sh
# Create a new cert chain, which contains both the signing and device public cert
cat signing-cert.pem > demo-device-007.chain.pem
cat demo-device-007.pem >> demo-device-007.chain.pem
# Create a new cert chain, which contains both the device public cert and the signing (in that order)
cat demo-device-007.pem > demo-device-007.chain.pem
cat signing-cert.pem >> demo-device-007.chain.pem

# Configure the cert chain file as the main cert to be used by thin-edge.io
tedge config set device.cert_path /etc/mosquitto/certs/demo-device-007.chain.pem
Expand Down