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

--certificate-path flag is not respected #244

Open
tom-aignostics opened this issue Jun 9, 2023 · 0 comments
Open

--certificate-path flag is not respected #244

tom-aignostics opened this issue Jun 9, 2023 · 0 comments

Comments

@tom-aignostics
Copy link

tom-aignostics commented Jun 9, 2023

When using a context or any command with a custom CA via --certificate-path it seems to not be respected. I tested with zed v0.10.1 but I think it also appears in the latest version.

E.g. running zed schema read --log-level trace fails with:

11:29AM DBG configured logging async=false format=auto log_level=trace provider=zerolog
11:29AM TRC token={"APIToken":"<API-TOKEN>","CACert":null,"Endpoint":"localhost:50051","Insecure":false,"Name":"my-context"}
11:29AM TRC requesting schema read request={}
[...]
Error: rpc error: code = Unavailable desc = connection error: desc = "transport: authentication handshake failed: x509: “<cert-alias>” certificate is not trusted"

Even setting --certificate-path directly on the call does not change this.

I could trace the issue back to

return Token{

I think one should carry over the CACert field from the CurrentToken response. If that's also your understanding I can open a PR.

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