Field based redaction
See original GitHub issueIt would be really nice to have a way to apply selective redaction (aka. hidden / secret values) on fields for classes marked @Serializable
. I realize that you can probably write your own custom serializers but this seems like functionality that should probably be “out-of-the-box”.
Coming from the java world, there are certain libraries that do this already (see example in java immutables), so it led me to request this feature here.
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Implement Field Level Redaction — MongoDB Manual
Implement Field Level Redaction ... The $redact pipeline operator restricts the contents of the documents based on information stored in the documents themselves....
Read more >RedactFields - IBM
The RedactFields action creates rectangular redaction fields to cover sensitive or restricted information in the document. These redactions and an audit ...
Read more >FIELD LEVEL REDACTION WITH EPHESOFT AND BOX
FIELD LEVEL REDACTION WITH EPHESOFT AND BOX. Home . Insights & Events . FIELD LEVEL REDACTION WITH EPHESOFT AND BOX. Search for: ...
Read more >Data Redaction: What It Is and When to Use It - Privitar
Data redaction is a data masking technique that enables you to mask (redact) data by removing or substituting all or part of the...
Read more >Guidance on Redacting Personal Data Identifiers in ...
Press Ctrl as you drag to select a line, a block of text, an object, or an area. Use this method to select...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
For this use-case you can write your own encoder that know what fields should be masked (based either on annotation or simply by field name) and masks them appropriately.
You should consider to write it
Logging looks out of scope, a
ToStringBuilder
is more appropriate, there are several implementations for JVM.