-
Notifications
You must be signed in to change notification settings - Fork 29
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
tls: failed to verify certificate: x509: certificate signed by unknown authority #405
Comments
Hm since it does not work may I recommend a workaround? To my understanding Go uses the systems CA store, so adding the signing cert there from the internal CA should allow to make it work. |
I figured it out, but there is some severe lack of documentation paired with implicit logic that makes this quite annoying to figure out. Firstly, it seems that zitadel-go uses the Fortunately zitadel-go, allows you to provide your own But then, when sending an actual API request, it fails again with the same error. Now HERE is where the
is actually required and used. So the following allows me to actually skip verification of the certificate chain and interact with Zitadel.
It is quite unfortunate that this is documented so poorly and essentially requires you to debug through the code in order to understand what is happening. |
I am trying to circumvent the server certificate check:
Unfortunately, it seems zitadel-go is ignoring the provided
tls.Config
and performs the server certificate validation anyways.Expectation
zitadel-go offering grpc.DialOptions to customize the underlying grpc connection should honour the provided configuration options.
The text was updated successfully, but these errors were encountered: