Pros and cons of various Consent storage methods

[Wessel, Keith]

We chose to use a database for this. With client storage, a user wouldhave to consent from each device they use whereas with a database, they consent once per service (or once overall if they chose that radio button). Memcache is lighter weight than a relational database, but it's still a dependency, and it didn't offer the robustness we wanted for server-side storage.

Keith


From: users <users-bounces at shibboleth.net> On Behalf Of Mark McCoy
Sent: Friday, April 19, 2019 3:43 PM
To: Shibboleth Users <users at shibboleth.net>
Subject: Pros and cons of various Consent storage methods

We are going to be upgrading our IdP during the summer, and we are looking to enable the user consent and/or terms of use features. 

Can anyone speak to the pros and cons of each of the three methods for storing the consent records (client-storage, memcached, database)? What are people using and what experiences have you had?

Respectfully,
Mark

Mark McCoy
OIT Manager, Platform Application Services
Office of Information Technology
The University of Texas at San Antonio