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
The certificates that are used for the web server connection are not rotated - which leads to the server refusing the connection once the certificates expire (especially if the certificates have short expiration timeframe - which is advisable for better security). Need to add something like fswatch to notice when the certificate has changed and reload it.
The text was updated successfully, but these errors were encountered:
I would advise against this though. It requires adding locks throughout the codebase. I would expect that rotating a certificate during an active connection may cause unexpected failures.
Can this be handled by the orchestration framework, restarting the server with the updated certificate?
Description
The certificates that are used for the web server connection are not rotated - which leads to the server refusing the connection once the certificates expire (especially if the certificates have short expiration timeframe - which is advisable for better security). Need to add something like fswatch to notice when the certificate has changed and reload it.
The text was updated successfully, but these errors were encountered: