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

Support AllowedCN and AllowedHostname through config file #17867

Closed
clwluvw opened this issue Apr 24, 2024 · 0 comments · Fixed by #17861
Closed

Support AllowedCN and AllowedHostname through config file #17867

clwluvw opened this issue Apr 24, 2024 · 0 comments · Fixed by #17861

Comments

@clwluvw
Copy link
Contributor

clwluvw commented Apr 24, 2024

What would you like to be added?

Allow setting AllowedCN and AllowedHostname tls fields through the config file for peer transport security.

Why is this needed?

According to the documents, flags cannot be mixed with a config file:

Caution: If you mix-and-match configuration options, then the following rules apply.
Command-line flags take precedence over environment variables.
If you provide a configuration file all command-line flags and environment variables are ignored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

1 participant