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
2.**Hostname Validation** - Verify an outbound server certificate CN/SAN matches the connection target (`validate-certificate-hostname`)
132
132
3.**Mutual Authentication** - Require both sides authenticate (`require-mutual-authentication`)
133
133
134
134
#### Decision Matrix: Which Combination to Use
@@ -151,10 +151,12 @@ When `validate-certificate-hostname = false` (the default):
151
151
152
152
When `validate-certificate-hostname = true`:
153
153
154
-
*Certificate CN (Common Name) or SAN (Subject Alternative Name) must match the target hostname
154
+
*The outbound server certificate CN (Common Name) or SAN (Subject Alternative Name) must match the target hostname
155
155
* Traditional TLS hostname validation as used in HTTPS
156
156
***Best for:** Client-server architectures with shared certificates and stable DNS names
157
157
158
+
Hostname validation is an outbound server-identity check: the connecting node knows the hostname it intends to reach. The receiving node does not have an independently known hostname for an inbound client, so this setting does not infer one from the client's IP address or certificate. Use a `DotNettySslSetup` custom validator when inbound clients must satisfy application-specific identity or authorization rules such as certificate pinning, subject/issuer checks, or an explicit expected identity.
159
+
158
160
**HOCON Example - P2P Cluster (Common Default):**
159
161
160
162
```hocon
@@ -370,7 +372,7 @@ Perform standard chain validation, then apply custom business logic:
370
372
371
373
#### Hostname Validation
372
374
373
-
Enable traditional TLS hostname validation (certificate CN/SAN must match target hostname). Use for client-server architectures with shared certificates:
375
+
Enable traditional outbound TLS hostname validation (the server certificate CN/SAN must match the connection target). Use for client-server architectures with stable DNS names:
0 commit comments