Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-23 08:58:41 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 111

Best practice Hydrant certificates (#34465)

Browse source 
Feedback from `customer-cisneros` on 2025-10-17
This commit is contained in:
Noah Talerman 2025-10-22 11:37:24 -04:00 committed by GitHub
parent 304d581d87
commit 2f8f268073
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 2 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
articles/connect-end-user-to-wifi-with-certificate.md
View file

@ -466,7 +466,8 @@ jq -r .certificate response.json > /opt/company/certificate.pem
This script assumes that your company installs a custom Company Portal app or something similar at `/opt/company`, gathers the user's IdP session information, uses username and a password to protect the private key from `/opt/company/userinfo`, and installs that the certificate in `/opt/company`. You will want to modify it to match your company's requirements.
The `userinfo` file in the scripts looks like the below. However, the variables could be loaded from the output of a command or even a separate network request depending on your requirements:
For simplicity, the scripts use a `userinfo` file (below). However, the best practice is to load variables from the output of a command or even a separate network request:
```shell
PASSWORD="<Password-for-the-certificate-private-key>"
USERNAME="<End-user-email>"