PPM Encryption Key
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7
- Forks
- 2
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 3
Description
Currently we don't explicitly manage the PPM encryption key. The PPM instance manages its own key and generates a new key during version upgrades. Tokens that we give to teams for remote administration, generated with rspm create-token, become invalidated against the server's new encryption key. (Discovered via internal Slack discussion)
Instead, we should explicitly generate and manage the encryption key for the instance and set it in the PACKAGEMANAGER_ENCRYPTION_KEY env var.
Official docs: https://docs.posit.co/rspm/admin/appendix/encryption/
This way all remote administration tokens we give to folks will continue working across server upgrades.
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 reviewing the repository's configuration and deployment code, then read the linked Posit encryption documentation to understand how PACKAGEMANAGER_ENCRYPTION_KEY should be generated and supplied. Done means the PPM instance uses an explicitly managed key so tokens created with rspm create-token remain valid after server upgrades; no test or file is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devops, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100