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
Almost all tools that rely on self-signed CA typically allow configuring a CA certificate along with server/client certificate and private key.
The behavior should be, if configured, the server/client should only trust the provided ca for certificate validation.
This way
My assumption is most people running bchd, would do so with intention of using the grpc endpoint for internal services.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Almost all tools that rely on self-signed CA typically allow configuring a CA certificate along with server/client certificate and private key.
The behavior should be, if configured, the server/client should only trust the provided ca for certificate validation.
This way
My assumption is most people running bchd, would do so with intention of using the grpc endpoint for internal services.
The text was updated successfully, but these errors were encountered: