Details
-
Technical Task
-
Status: Closed
-
Minor
-
Resolution: Completed
-
None
-
AppSec Iteration 83, AppSec Iteration 84, AppSec Iteration 85, AppSec Iteration 86, AppSec Iteration 87, AppSec Iteration 88, AppSec Iteration 89, AppSec Iteration 90, AppSec Iteration 91, AppSec Iteration 92, AppSec Iteration 93
Description
Description
Change the API to make it possible to handle all the cookies according to the End Users' cookie setting preferences on the server side. This technically means an additional parameter, the cookie type to the existing API. In addition to that the End Users' cookie preferences must be checked in the API also.
Dependencies
- Storing the cookie preferences on client side - We have a dependency with the LoL here. (
LPS-142518). - Site level configuration (
LPS-148285)
Design
This story doesn't have design aspect. The design is here to have a reference for the configuration.
https://www.figma.com/file/BFiKtvHk2qJqdI7FqAt4wC/?node-id=141%3A20553
Acceptance Criteria
- AC-1 (Current logic)
- Given the cookie preference handling feature is disabled (inactive)
- When a feature, function wants to add a cookie in the server side logic (Java)
- Then the cookie should be added.
- AC-2
- Given the cookie preference handling feature is enabled (active)
- When the End User's cookie handling preferences have been set
- Then the End User's cookie handling preferences have to be considered at adding the cookie.
- AC-2
- Given the cookie preference handling feature is enabled (active)
- When the End User's cookie handling preferences have not been set
- Then the "Consent Mode" at site level Cookie configuration at the the Banner configuration must be considered at adding cookie.