[MGNLPN-410] Use GDPR-compliant cookie manager Created: 20/Feb/18  Updated: 13/Jun/18  Resolved: 12/Jun/18

Status: Closed
Project: Magnolia Personalization
Component/s: Traits
Affects Version/s: None
Fix Version/s: 1.6

Type: New Feature Priority: Neutral
Reporter: Antti Hietala Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
causes MGNLPN-423 Regression: can't choose a cookie val... Closed
dependency
is depended upon by MGNLDEMO-286 Use GDPR-compliant cookie manager Closed
relation
is related to MGNLPRIV-2 Client-side consent collection and st... Closed
Template:
Acceptance criteria:
Empty
Documentation update required:
Yes
Date of First Response:
Epic Link: GDPR consents
Sprint: Kromeriz 148, Kromeriz 149, Kromeriz 151
Story Points: 5

 Description   

Use a GDPR-compliant cookie manager to handle cookies.

  • Visitor trait is using cookie manager for handling cookies
    • Cookies configured under visitor filter are migrated to cookie module config
  • Cookie trait is using link field to the cookie app instead of the hardcoded cookie names and values
    • cookie trait is migrated to use just ruleField(cookieId) instead of the cookieName/cookieValue part -> no custom transformer needed


 Comments   
Comment by Roman Kovařík [ 20/Apr/18 ]

Closing as we don't have any mechanism to include cookies in personalization module, just cookie detection.
The implementor of cookie insertion should be responsible for requesting consent.

Comment by Roman Kovařík [ 31/May/18 ]

For documentation: the cookie and visitor traits are now using cookie manager (possible screenshot update for the cookie trait..if there are?).

Comment by Roman Kovařík [ 11/Jun/18 ]

Reopened: adjust to changes by MGNLPRIV-26.

Generated at Mon Feb 12 06:37:22 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.