Skip to content

CamelKafkaConnectMain is showing sensitive information in summary #973

Closed
@oscerd

Description

@oscerd

[2021-02-04 08:41:37,479] INFO Setting initial properties in Camel context: [[connector.class=org.apache.camel.kafkaconnector.aws2kms.CamelAws2kmsSinkConnector, camel.sink.endpoint.operation=createKey, camel.sink.component=aws2-kms, value.converter=org.apache.kafka.connect.storage.StringConverter, key.converter=org.apache.kafka.connect.storage.StringConverter, camel.component.aws2-kms.access-key=<plain_accesskey_key>, camel.component.aws2-kms.secret-key=<plain_secret_key>, topics=kms9000, camel.sink.path.label=kms-point, task.class=org.apache.camel.kafkaconnector.aws2kms.CamelAws2kmsSinkTask, name=CamelAws2-kmsSinkConnector, camel.component.aws2-kms.region=eu-west-1]]

This is because the SensitiveUtils class take into account the camel case version sensitive names like accessKey or secretKey, but in this case the filter should be for kebab cases. I think we need to improve this on camel-side.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions