We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug Configuration tile in UI shows TLS Disabled, for instance where TLS wasn't disabled.
To Reproduce Steps to reproduce the behavior:
VAULT_LOCAL_CONFIG
Expected behavior TLS should be Enabled.
Environment:
vault status
vault version
Vault server configuration file(s):
api_addr = "https://${vault_domain}" cluster_name = "${vault_cluster_name}" ui = true log_level = "info" log_format = "json" listener "tcp" { address = "[::]:${vault_port}" cluster_address = "[::]:${vault_port + 1}" tls_cert_file = "/etc/vault/tls/vault.crt" tls_key_file = "/etc/vault/tls/vault.key" tls_disable_client_certs = "true" proxy_protocol_behavior = "use_always" } seal "awskms" { region = "${aws_region}" kms_key_id = "${kms_key_id}" } storage "dynamodb" { ha_enabled = "true" region = "${aws_region}" table = "${vault_dynamodb_table}" }
Additional context None.
The text was updated successfully, but these errors were encountered:
I confirm - I have the same behavior
Sorry, something went wrong.
I am seeing the same behavior on on Vault 1.15.0+ent
config snippet:
listener "tcp" { address = "0.0.0.0:8200" ### Enable TLS ### tls_cert_file = "./tls/cert.pem" tls_key_file = "./tls/key.pem" tls_client_ca_file = "./tls/ca.pem" tls_disable_client_certs = false }
Seeing the same issue, Does anyone know the reason?
Successfully merging a pull request may close this issue.
Describe the bug
Configuration tile in UI shows TLS Disabled, for instance where TLS wasn't disabled.
To Reproduce
Steps to reproduce the behavior:
VAULT_LOCAL_CONFIG
.Expected behavior
TLS should be Enabled.
Environment:
vault status
): 1.15.0vault version
): IrrelevantVault server configuration file(s):
Additional context
None.
The text was updated successfully, but these errors were encountered: