Details
-
Improvement
-
Resolution: Fixed
-
Major
-
6.5.0
Description
It would be helpful to be able to optionally exclude sensitive entries when getting metakv entries in a directory. This would allow logging of iterated entries without inadvertently exposing a sensitive entry.
Attachments
| For Gerrit Dashboard: MB-37677 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 127545,3 | MB-37677 create V2 iteration methods that return Sensitive | mad-hatter | cbauth | Status: MERGED | +2 | +1 |
| 127546,3 | MB-37677 fix debug /_list endpoint to return values as strings, not | mad-hatter | cbauth | Status: MERGED | +2 | +1 |
| 127547,4 | MB-37677 add debug endpoint /_changesV2/ to test | mad-hatter | cbauth | Status: MERGED | +2 | +1 |
| 127548,2 | MB-37677 GET /_metakv endpoint to return sensitive when iterating | mad-hatter | ns_server | Status: MERGED | +2 | +1 |
| 127648,1 | Merge remote-tracking branch 'gerrit/mad-hatter' | master | cbauth | Status: MERGED | +2 | +1 |