HDDS-4788. Enable mTLS for Ratis in OM HA #1912
Merged
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.
What changes were proposed in this pull request?
Let OM HA enable TLS for its internal Ratis if
SecurityConfig#isGrpcTlsEnabledis true (ie. ifhdds.grpc.tls.enabled=true)To make this work in docker-compose cluster, we need a small tweak in the OM certificate request. Normally hostname is included in the alternative names list, and subject name can be anything (in our case it's in the form of
user@host, eg.root@om1). However, if reverse lookup for OM host's IP does not work, then subject name will be the only information available for certificate verification to match DNS. In this case we should omit the username part, because it will cause DNS match to fail.https://issues.apache.org/jira/browse/HDDS-4788
How was this patch tested?
Enabled
hdds.grpc.tls.enabled=trueinozonesecure-om-hacluster.https://github.com/adoroszlai/hadoop-ozone/actions/runs/547953101