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.

Sign up for GitHub

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

Jump to bottom

Do not log getPayload as INFO for security reasons. #273

Open

kaladay opened this issue Dec 19, 2024 · 1 comment · Fixed by folio-org/mod-camunda#131

Assignees

kaladay commented Dec 19, 2024

The packet bodies may contain private information.

This getPayload should not be normally logged.

Change the logging to DEBUG or remove logging entirely.

see: https://github.com/folio-org/mod-camunda/blob/904057a162a0709d6bb551c3ef10cba5b4aa4d63/src/main/java/org/folio/rest/camunda/kafka/EventConsumer.java#L37

The text was updated successfully, but these errors were encountered:

wwelling mentioned this issue

Issue #273: Change event consumer payload log to debug #274

Closed

kaladay assigned wwelling

wwelling commented Dec 19, 2024 •

edited

Loading

Shouldn't we be encrypting secrets for data at rest or in transit?

wwelling linked a pull request

that will close this issue

Change event consumer payload log to debug folio-org/mod-camunda#131

Merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment