HDDS-3997. Ozone certificate needs additional flags and SAN extension… #1235
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
|
+1 for the patch. |
jnp
approved these changes
Jul 24, 2020
|
Thanks @jnp for the review. I will merge the PR shortly. |
timmylicheng
pushed a commit
that referenced
this pull request
Aug 6, 2020
rakeshadr
pushed a commit
to rakeshadr/hadoop-ozone
that referenced
this pull request
Sep 3, 2020
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.
… for GRPC TLS.
What changes were proposed in this pull request?
Adding SAN extension for SCM issued certificate and add DN certificate with sign/encrypt flag to meet requirement of SSL handshake with GRPC/Netty.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-3997
How was this patch tested?
Test with real cluster before patch HDDS-3996 and HDDS-3997. Certificate does not have the required extension and flag, which fail the SSL handshake for Ratis operations like addGroup, leader election when ozone.grpc.tls.enabled is true.
After the patch, verified the RATIS-Three pipeline can be created successfuly without SSL error.