You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a server knows it can go into provisioning mode - either build settings or via jwt - it should note the expiry age of its certificate and near expiry re-enter provisioning.
Lets say the cert is valid for 7 days at start and the cert was obtained through provisioning, on the last day of cert validity it should at a random duration before expiry re-enter provisioning mode.
This means if 10k machines were provisioning at the same time - a week later they will gradually, spread over several hours, reprovision themselves to get new certs.
The text was updated successfully, but these errors were encountered:
When a server knows it can go into provisioning mode - either build settings or via jwt - it should note the expiry age of its certificate and near expiry re-enter provisioning.
Lets say the cert is valid for 7 days at start and the cert was obtained through provisioning, on the last day of cert validity it should at a random duration before expiry re-enter provisioning mode.
This means if 10k machines were provisioning at the same time - a week later they will gradually, spread over several hours, reprovision themselves to get new certs.
The text was updated successfully, but these errors were encountered: