Add TLS/mTLS support to CLI client
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 344
- Forks
- 47
- Avg merge
- 4d 4h
- Merged PRs (30d)
- 26
Description
Context
The ConnectRPC server supports TLS via tls_cert_file, tls_key_file, and tls_client_ca_file config options. However, the CLI client has no way to specify a custom CA certificate or client certificate for connecting to a TLS-enabled server.
The old gRPC createConnection() had a caCertFile parameter but it was never wired up — both createClient and createAdminClient always passed "".
Proposal
Add CLI flags (or config options) to support:
--ca-cert— Path to a custom CA certificate file (for self-signed or internal CAs)--client-cert/--client-key— For mTLS (optional, lower priority)--insecure— Skip TLS verification (dev only)
These should be configurable via both CLI flags and ~/.config/raystack/frontier.yml.
Related
- PR #1388 (CLI migration to ConnectRPC) — noted as not a regression since it was never functional
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reviewing the CLI client migration in PR #1388 and the old gRPC createConnection(), createClient, and createAdminClient paths, then inspect the configuration handling for ~/.config/raystack/frontier.yml. Define how the CA, client certificate/key, and insecure settings flow through both CLI flags and config, with successful TLS and mTLS connections as the completion criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100