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.

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

Secured properties must not be exposed #68

Open
artem-v opened this issue Jun 7, 2018 · 0 comments
Open

Secured properties must not be exposed #68

artem-v opened this issue Jun 7, 2018 · 0 comments
Labels

Comments

@artem-v
Copy link
Contributor

artem-v commented Jun 7, 2018

With addition of config-vault module we started to support secured properties. There are places in the library where name and value of config property are exposed: config_listener, jmx exposer, http_server and plain log occurences. It's bad idea to show plain decrypted prop value in the log while keep it encrypted in Vault.

In this ticket.
Get rid of places where pconfig property values are exposed. This includes: audit log entires. plain library debug log entries, http server must not expose prop values, jmx shoulnd't expose prop values.

@artem-v artem-v added the bug label Jun 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant