You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Changed
Schema generation now refuses conflicting protection on concept-typed properties, as it already does on other properties. An [Encrypted] scope on the property that differs from the scope on its concept type fails with a clear error naming the property and both scopes, and so does combining [PII] and [Encrypted] across the property and its concept type. (part of #5623)
Security
[PII] and [Encrypted] on a property or record parameter whose type is a ConceptAs<T>, or a collection of such concepts, are now kept in the event type's schema, so those values are protected when they are appended. Before this fix, the attribute was silently dropped and the value was stored in plain text; it was only applied when the attribute was on the concept type itself. (#5623)
Events appended before this upgrade are not re-encrypted. Their values stay in plain text and are not removed when a subject's key is erased. Review event types that put [PII] or [Encrypted] on a concept-typed property or a collection of concepts, since their earlier events hold those values unprotected. (part of #5623)