opendevstack / opendevstack/ods-core
Passwords in Prov App ConfigMap
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 53
- Forks
- 34
- Avg merge
- 3h 26m
- Merged PRs (30d)
- 1
Description
Is your feature request related to a problem? Please describe.
All sensitive information such as passwords should be moved out of the Provisoning Application's Config Map application.properties into a Secret resource. Examples that I found are:
- crowd.application.password
- jasypt.encryptor.password
- spring.mail.password
Describe the solution you'd like
Create a secret that holds the sensitive information required by the Provisioning Application.
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 locating the Provisioning Application's application.properties and the ConfigMap that supplies it, then trace how the application currently receives crowd.application.password, jasypt.encryptor.password, and spring.mail.password. Done means the sensitive values are held in a Kubernetes Secret and are no longer stored in the ConfigMap.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, spring
- Domain
- infrastructure, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100