mirror of
https://github.com/fleetdm/fleet
synced 2026-05-23 17:08:53 +00:00
e514fc4881
For https://github.com/fleetdm/fleet/issues/27984 # Checklist for submitter If some of the following don't apply, delete the relevant line. <!-- Note that API documentation changes are now addressed by the product design team. --> - [x] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. See [Changes files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/Committing-Changes.md#changes-files) for more information. - [x] Input data is properly validated, `SELECT *` is avoided, SQL injection is prevented (using placeholders for values in statements) - [x] If paths of existing endpoints are modified without backwards compatibility, checked the frontend/CLI for any necessary changes - [x] Added/updated automated tests - [x] A detailed QA plan exists on the associated ticket (if it isn't there, work with the product group's QA engineer to add it) - [x] Manual QA for all new/changed functionality
1 line
585 B
Text
1 line
585 B
Text
Fleet-managed Custom SCEP CA certificates will be renewed 30 days before expiry for those valid longer than 30 days or when half the validity period remains for certificates valid 30 days or less. This only applies to certificates that were requested after this renewal feature was added. For hosts with Custom SCEP CA certificates requested prior to this renew feature, updating the profile to contain the $FLEET_VAR_SCEP_RENEWAL_ID variable in the CN and then manually resending the profile will generate a new certificate which will be automatically renewed before its next expiry.
|