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
{{ message }}
This repository has been archived by the owner on Nov 30, 2022. It is now read-only.
MUST require that a given DRP action is only used once (this ensures a 1:1 match from DRP actions to Fidesops policies)
MUST validate the action against the list of valid actions defined in the DRP specification
SHOULD NOT require that DRP actions are defined; it is valid to have multiple Fidesops policies defined but none mapped to a DRP action
SHOULD NOT ascribe any specific behaviour to this DRP action, it is purely to translate between standards-based DRP actions and the user-defined policies in Fidesops
Implementation Notes
includes ingesting - the whole flow to associating an action with a policy
SQLAlchemy will allow us to specify that the DRP action field as unique.
@adriaaaa one bit of clarification- by "focus", do you mean we should only support access and deletion rights for now? i.e not access:categories, for example?
Requirements
action
will be equivalent to theright
column from the spec. here: https://github.com/consumer-reports-digital-lab/data-rights-protocol#301-supported-rights-actions and we should only focus onaccess
anddelete
.Implementation Notes
The text was updated successfully, but these errors were encountered: