Integrate the new dynamic migrid key/certificate fingerprints from files #77
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…les to allow fully automatic certificate renewal e.g. with LetsEncrypt. MiG user pages are then configured to always read and display the current fingerprint from associated fingerprint files. Relies on a version of migrid where fingerprints from file (PR 171) is already merged in. Requires either use of the included migcheckssl cron job or a similar renewal hook to write the certificate fingerprint to a fixed path upon renewal. Additionally further honor key/certificate collections marked with the special '.persistent' file marker in the provided certs/ or SITECERTS dir. Files there will be copied and used verbatim with nothing re-generated or truncated if so.
rasmunk
reviewed
Jan 7, 2025
jonasbardino
deleted the
adjust/integrate-keycert-fingerprint-files-and-further-honor-persistent-certs-marker
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Integrate the new dynamic migrid key/certificate fingerprints from files to allow fully automatic certificate renewal e.g. with LetsEncrypt. MiG user pages are then configured to always read and display the current fingerprint from associated fingerprint files.
Relies on a version of migrid where fingerprints from file (ucphhpc/migrid-sync#171) is already merged in.
Requires either use of the included
migchecksslcron job or a similar renewal hook to write the certificate fingerprint to a fixed path upon renewal.Additionally further honor key/certificate collections marked with the special
.persistentfile marker in the providedcerts/dir. Files there will be copied and used verbatim during build with nothing re-generated or truncated if so.