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

Option server_config.ssl.hostname_validation: false seems not to work #95

Open
MarkusNeuron opened this issue Sep 20, 2023 · 0 comments

Comments

@MarkusNeuron
Copy link

Hi,

we are evaluating the admin-console for productive use and need to connect from external (with a valid CN in the certificate) but also need to go cluster internal via service where the hostname does not match the certificate.

configured:

config:
  server_config:
     ssl:
       hostname_validation: false
       verify_certs: false # also tried optionally

Still getting the error when connecting internal:

[HPM] Error occurred while proxying request pulsar-admin-console-prod01-***/admin/v2/tenants to https://prod01-broker.prod01-***.svc.cluster.local:8443/ [ERR_TLS_CERT_ALTNAME_INVALID] (https://nodejs.org/api/errors.html#errors_common_system_errors)

Should not the hostname_validation: false setting avoid exactly that issue?

PS: Also set verify_certs: false but also did not help.

@MarkusNeuron MarkusNeuron changed the title Option server_config.ssl.hostname_validation = false seems not to work Option server_config.ssl.hostname_validation: false seems not to work Sep 20, 2023
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

No branches or pull requests

1 participant