mirror of
https://github.com/fleetdm/fleet
synced 2026-04-21 13:37:30 +00:00
Add note about server private key (#42865)
To deploy certificates, you must have a server private key setup or GitOps errors with 'Error: applying certificate authorities: POST /api/latest/fleet/spec/certificate_authorities received status 500 crypto/aes: invalid key size 0: crypto/aes: invalid key size 0'
This commit is contained in:
parent
eba4fad885
commit
c33e6150df
1 changed files with 2 additions and 0 deletions
|
|
@ -6,6 +6,8 @@ Fleet can help your end users connect to third-party tools like Wi-Fi or VPN by
|
|||
|
||||
Fleet will automatically renew certificates on Apple (macOS, iOS, iPadOS), Windows, and Android hosts before expiration. Learn more in the [Renewal section](#renewal).
|
||||
|
||||
To deploy certificates on a self-hosted Fleet instance, you'll need to configure a [server private key](https://fleetdm.com/docs/configuration/fleet-server-configuration#server-private-key).
|
||||
|
||||
Currently, these are supported platforms for each certificate authority:
|
||||
- **Okta**: macOS, iOS, and iPadOS
|
||||
- **DigiCert**: macOS, iOS, and iPadOS
|
||||
|
|
|
|||
Loading…
Reference in a new issue