[opencms-dev] Guidance on storing Klaro cookie-consent decisions in OpenCms database (Master’s thesis)

[Michael Emmerich]

Hello Zoya,

I do not know Klaro, but worked with other cookie consent tools in 
OpenCms before (commercial and self developed ones).

Could you please tell, why you want to persist user consent decisions in 
the OpenCms backend database?

Usually, cookie consent tools store their settings in a cookie. Which 
makes sense, as usually users who visit the website could not be 
identified to access the stored data again.

This would be different if you have a personalized website where users 
have to log in (e.g. extranets). Is this what you are implementing?

Or are you talking of keeping track of all user actions in the cookie 
consent tool for documentation?

Wold help if you could explain our use case a bit more.


Kind regards,

Michael


Am 09.09.25 um 11:05 schrieb zoya asadi via opencms-dev:
>
> Dear OpenCms team,
>
> I’m a Master’s student working on my thesis at the University of 
> Passau. As part of my project, I’m building a small website on OpenCms 
> and integrating the Klaro consent manager to handle cookie consent. I 
> understand the site normally uses Alkacon Software’s (Mercury) privacy 
> banner, but for my thesis I’m replacing it with Klaro.
>
> My goal is to persist each user’s consent decisions in the 
> OpenCms-backed database (e.g., MySQL) so the backend can read them and 
> enforce preferences server-side. What is the simplest recommended way 
> to do this? A short example or a link to documentation would be great.
>
> Thank you!
>
> Best regards,
>
> Zoya Asadi
>
> M.Sc. student, University of Passau
>
>
-- 
Michael Emmerich
  
-------------------

Alkacon Software GmbH & Co. KG - The OpenCms Experts
http://www.alkacon.com
http://www.opencms.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencms.org/pipermail/opencms-dev/attachments/20250910/24e3b6fd/attachment.htm>