Skip to content

fix: always redact sensitive rejected values - #1

Draft
brownie-cake wants to merge 2 commits into
mainfrom
agent/redact-sensitive-rejected-values
Draft

fix: always redact sensitive rejected values#1
brownie-cake wants to merge 2 commits into
mainfrom
agent/redact-sensitive-rejected-values

Conversation

@brownie-cake

Copy link
Copy Markdown

What

Add a sensitive-property denylist to DefaultValidationRejectedValueSanitizer.

Why / root cause

When the diagnostics switch exposeRejectedValue was enabled, rejected passwords, tokens, secrets, and credentials could be reflected into validation responses or logs. The global exposure switch overrode the secure default.

Impact

  • Ordinary fields can still be exposed when explicitly enabled.
  • Sensitive paths remain omitted regardless of the global switch.
  • Covers nested and separator variants such as credentials.clientSecret and oauth.access_token.

Checks

  • mvn -q -o -pl flyfish-validation-spring-support -am test
  • Added regressions for ordinary and sensitive rejected values.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants