Connecting to a private-CA mecatui server requires retyping the TLS CA path on every connection
@JAORMX is already working on this.
Since Sep 8, 2026.
- Dominant language
- Go
- Stars
- 152
- Forks
- 16
- Avg merge
- 14h 48m
- Merged PRs (30d)
- 536
Description
The problem
Logging in to a remote target once with mecatui login ADDRESS ... is a one-time thing -- after that, mecatui connect ADDRESS reconnects without needing to repeat any of the OIDC details.
But if the server is on a private CA, every single connect still needs:
mecatui connect ADDRESS --tls --tls-ca <server-ca>
typed out in full, for the life of that target. It's not a one-time setup cost like login -- it's a permanent tax on every reconnect, for a value that never changes for that target.
Impact
In practice this means either retyping the same long command every time, or building my own workaround (shell alias, script, etc.) just to get back to a plain mecatui connect ADDRESS.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.