In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.

Bug report

For bug reports, provide this information, please:

What Debezium connector do you use and what version?

Debezium standalone server

What is the connector configuration?

N/A

What is the captured database version and mode of deployment?

(E.g. on-premises, with a specific cloud provider, etc.)

N/A

What behavior do you expect?

Ability to mask/hide any custom sensitive config property form being logged. 

What behavior do you see?

Not able to mask/hide a custom sensitive config property from logging. 

Do you see the same behaviour using the latest released Debezium version?

(Ideally, also verify with latest Alpha/Beta/CR version)

2.7.3.Final

Do you have the connector logs, ideally from start till finish?

(You might be asked later to provide DEBUG/TRACE level log)

Not shareable log.

How to reproduce the issue using our tutorial deployment?

Provide a custom sensitive config property (e.g.: application.custom.credentials) which is not covered in the hardcoded password pattern of the io.debezium.config.Configuration interface.

Feature request or enhancement

For feature requests or enhancements, provide this information, please:

Which use case/requirement will be addressed by the proposed feature?

Hide/mask any custom sensitive config properties from being exposed during logging out.

Implementation ideas (optional)

<Your answer>