FieldMask JSON hops: preserve the field path the user selected
Check preservation of selected field paths rather than successful mask transmission.
Retain the selection before the final string
Check preservation of selected field paths rather than successful mask transmission. Do not silently turn a noncanonical path into another approved path. Supply Truthound with original and per-hop values instead of only the final string; transport success is not permission enforcement. [1, 2, 3]
The reported path drift
Protobuf #27437 reports noncanonical FieldMask paths drifting through successive JSON hops on v36-dev, including __Y becoming __y and then _y. Canonical paths are unaffected. The report does not establish an exploit or certify overall permission safety; keep its transformation evidence separate from the possible risk. [1]
Admission before conversion
Match approved source paths with decoded paths after each JSON hop and prevent shifted masks from reaching downstream projection. Preserve the source path and descriptor, defining canonical admission before conversion rather than concealing an unauthorized normalization inside the rule. [1, 3]
A hop referenced to __Y
The illustrative original path is __Y. Under a test contract promising preservation instead of rejecting this noncanonical input, expected path remains __Y. That passes; __y after the first hop fails. A production policy may instead reject noncanonical input, recording that rejection as a separate valid result. [1, 3]
Path reconciliation separate from authorization
Truthound Core Python SDK 3.3.2 can compare prepared approved_field_path and decoded_field_path with ColumnPairValidator using relationship="==". The operator extracts paths, maps descriptors and handles missing observations. The SDK does not repair the parser or enforce permissions, and matching paths do not certify absence of private-data disclosure. [1, 2, 3]
Rejection can be an explicit contract
Reject noncanonical paths under a canonical-only policy or declare a versioned mapping explicitly. Do not generalize the drift to inputs already restricted to canonical paths. Preserve separate checks of actual selected fields and authorization. [1, 3]
Application conditions
Preserve original paths and descriptors, defining canonical admission before JSON transformation.
Alternatives
Reject noncanonical input or apply an explicit versioned mapping.
Limitations
The SDK does not repair parsing or enforce permissions; path equality does not certify privacy or authorization.
Evidence
- Event checked
- Subject checked
- Modified
