Skip to content

Secured properties must not be exposed #68

@artem-v

Description

@artem-v

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions