-
Notifications
You must be signed in to change notification settings - Fork 2
Open
Description
The current design enforces that preferences are signed with the PAF id.
The rationale is to avoid a fraudulent actor taking a valid (signed) preferences object and attempting to reuse it for a user that did not set their preferences, or did set a different preferences value.
Or, more problematic, would take the preferences object and use it for all website visitors.
When signing preferences with ids, we ensure the value of the preference was set for a particular user.
This comes with some constraints:
- preferences can't exist without ids (see For "this site only" why would the preferences and the identifiers be needed? OneKey-implementation#115)
- when simply changing the id, preferences need to be re-signed (https://github.com/prebid/paf-mvp-implementation/pull/120/files/5fb8a059d1d70fa226c13aba8c9655baad2ef549#diff-21193811b758f6d40b39e174d4b5622f8b741a520255c5351f18056bf93fe4c8R439)
I think the advantages outweigh the drawbacks but the question has been raised in implementation.
Metadata
Metadata
Assignees
Labels
No labels