Support Self-signed Certs
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7
- Forks
- 2
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 3
Description
Issue
When customers use self-signed certificates for Posit products, Workbench cannot publish to Connect instances secured with these certificates unless they're explicitly trusted.
Current Workaround
Currently, users can manually upload certificates via Workbench UI (Tools > Global Options > Publishing)
Proposed Solution
Implement automation to pre-load trusted certificates into Workbench sessions, eliminating the manual step for users. We might be able to use session init containers to ensure each new session trusts the workload's certs. There's some existing documentation for doing this by running update-ca-certificates on the server with the appropriate certs present.
Supporting Docs
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.
Research direction
Start by locating the session init-container configuration in the repository and review the existing guidance for running update-ca-certificates with the required certificates. Define how certificates would be made available to each Workbench session and verify that publishing to a Connect instance using a self-signed certificate works without the manual UI upload.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- infrastructure, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100