[MGNLPRIV-51] cookieConsent_status does not set cookies if more than one value is provided Created: 26/Oct/20  Updated: 14/Dec/23  Resolved: 14/Dec/23

Status: Closed
Project: Privacy
Component/s: None
Affects Version/s: 2.0
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Richard Gange Assignee: Khayal Musayev
Resolution: Not an issue Votes: 1
Labels: to-verify
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLDEMO-349 Showcase consent for different groups... Open
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Epic Link: Privacy maintenance
Team: AdminX
Work Started:

 Description   

When using the technique of providing multiple values as outlined in the documentation under Consent for different groups of cookies the cookies are not properly set if more than one value is provided.

  • features
  • features,marketing
  • features,marketing,statistics
  • marketing,statistics

According to the documentation values can be separated with a comma "," but this does not work. Only providing a single value sets the cookie.



 Comments   
Comment by Matt Rajkovic [ 30/Jan/23 ]

Asked rgange if this issue is still valid / needed?

Comment by Evzen Fochr [ 08/Dec/23 ]

Because of:
With Version 0 cookies, values should not contain white space, brackets, parentheses, equals signs, commas, double quotes, slashes, question marks, at signs, colons, and semicolons.
cookie that contain such valu has empty value on server side. https://javaee.github.io/javaee-spec/javadocs/javax/servlet/http/Cookie.html#:~:text=With%20Version%200%20cookies%2C%20values,same%20way%20on%20all%20browsers.
Fix for this issue would be set cookie version to 1 in application server or use different separator (it works with | like "features|marketing")

Generated at Mon Feb 12 10:31:11 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.