Description
If you bootstrap with an IP (and not an FQDN) and are using TLS, the client will fail with a RemoteCertificateNameMismatch because the certificates name doesn't match the IP. As a work-around for test environments, we can add a flag that ignores this error and allows the client to not fail when establishing the TLS connection.
Attachments
Issue Links
- has to be done before
-
NCBC-1117 HttpServerConfig Doesn't Validate Server Certificate
- Resolved