restatedev / restatedev/journal-encryption
Integrate Decryption Service with Cloud Auth
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Currently, we expect users to deploy this server inside private infra, so it is not publicly accessible. Users would need to connect via VPN to that infra, to let their web browser contact the decryption service.
Proposed Change
- The Web UI passes the the auth token from the UI and the environment ID to the the decrypt endpoint
- The decryption service can call the cloud APIs (like
DescribeEnvironment) to check if the token is valid for that environment. - Only once validated will the service decrypt the requested data
We would also need to ensure that any key caching code token/env aware, meaning the key cache should exist per env_id/token combination.
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 tracing the Web UI decrypt endpoint and the decryption service's key-cache code, then inspect how cloud API calls can validate an environment and token. Done means the endpoint passes the token and environment ID, validation occurs before decryption, and cached keys are scoped to each environment/token combination.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication, cloud, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100