Added doc note regarding HTTP message signature performance. (#31905)

This commit is contained in:
Victor Lyuboslavsky 2025-08-18 19:26:39 -05:00 committed by GitHub
parent 2164828981
commit 8246fa4fe2
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -341,6 +341,7 @@ fleetctl package \
- SCEP certificate requests can be throttled by the [osquery_enroll_cooldown](https://fleetdm.com/docs/configuration/fleet-server-configuration#osquery-enroll-cooldown) server option, similar to how fleetd enrollments are throttled
- When a host requests a host identity certificate, the server will expect all future traffic from that host to be signed with HTTP message signatures. This allows mixed environments where some hosts use managed client certificates and others do not
- Fleet administrators can enforce HTTP message signature requirements server-wide using the [auth.require_http_message_signature](https://fleetdm.com/docs/configuration/fleet-server-configuration#auth-require-http-message-signature) server configuration option
- HTTP message signatures use P384 elliptic curve cryptography by default, which requires additional CPU resources to verify on the Fleet server. This can impact performance and should be considered when planning your Fleet deployment.
### Specifying update channels