Users should not supply auth token in chains-config configMap in plaintext
Open
Nobody has claimed this yet.
kind/feature
- Dominant language
- Go
- Stars
- 277
- Forks
- 164
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 61
Description
Feature request
As of today vault token is supplied via the signers.kms.kmsref.auth.token field which is not very ideal as it stores the token in clear text
This can also be true for other tokens as well
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
The request centers on the chains-config ConfigMap and the signers.kms.kmsref.auth.token field. Start by locating how that field and other token fields are read; the issue does not identify files, tests, an entry point, or the intended secure configuration design.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100