Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DB-26-16] Log an error when node certificate is not a valid server certificate #4249

Merged
merged 2 commits into from May 16, 2024

Conversation

hayley-jean
Copy link
Member

@hayley-jean hayley-jean commented May 3, 2024

Added: Log an error when the node certificate is not a valid server certificate

Update the documentation to include the stricter certificate requirements.

If you provide a node certificate with invalid key usages (e.g. missing a required key usage), the server will now log an error:

[24448,26,12:47:42.882,ERR] Connection from node: "127.0.0.1" was denied because it is not configured as a valid server certificate: "Missing key usage: Digital Signature"

The error is only logged if the provided certificate matches the reserved node common name, and has IP or DNS addresses in the SAN.

@hayley-jean hayley-jean self-assigned this May 3, 2024
@hayley-jean hayley-jean changed the title Log an error when node certificate is not a valid server certificate [DB-26-16] Log an error when node certificate is not a valid server certificate May 3, 2024
@hayley-jean hayley-jean force-pushed the hayley-jean/add-key-usage-error-logs branch from 10e6a30 to 4fd77ee Compare May 3, 2024 12:58
@hayley-jean hayley-jean force-pushed the hayley-jean/add-key-usage-error-logs branch from 20a7e1b to 720ad5d Compare May 14, 2024 13:59
@timothycoleman timothycoleman merged commit 44e5326 into master May 16, 2024
8 checks passed
@timothycoleman timothycoleman deleted the hayley-jean/add-key-usage-error-logs branch May 16, 2024 11:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants