Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Task] Database should require PG_ENCRYPT_KEY and bail out if none provided #128

Closed
andrewazores opened this issue Oct 25, 2023 · 0 comments · Fixed by #129
Closed

[Task] Database should require PG_ENCRYPT_KEY and bail out if none provided #128

andrewazores opened this issue Oct 25, 2023 · 0 comments · Fixed by #129
Assignees
@andrewazores
Labels
feat New feature or request

Comments

@andrewazores
Copy link
Member

Describe the feature

For data safety and integrity, the cryostat3-db image should require the user provide the PG_ENCRYPT_KEY environment variable used for encrypting the JMX credentials keyring. There should be no default value, so that the user or deployment system is forced to make this choice and provide an encryption key.

Anything other information?

No response
@andrewazores andrewazores added the feat New feature or request label Oct 25, 2023
@andrewazores andrewazores self-assigned this Oct 25, 2023
@andrewazores andrewazores moved this to In Progress in 3.0.0 release Oct 25, 2023
@andrewazores andrewazores mentioned this issue Oct 25, 2023
Merged
7 tasks
@github-project-automation github-project-automation bot moved this from In Progress to Done in 3.0.0 release Oct 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@andrewazores andrewazores

Labels
feat New feature or request
Projects
No open projects
3.0.0 release
Status: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat(db): inherit from scl image, enforce PG_ENCRYPT_KEY andrewazores/cryostat3
1 participant
@andrewazores