Consent Configuration

[Jim Fox]

> Unfortunately, we have a very fickle user base - and when turning on the attribute consent release -- they only expected to be asked once if
> option selected, and if challenged again, when using another of their multiple devices/browsers -- the technology will be blamed :(
> 
> Is it possible to store consent in a database and verify? Or the only option is persistent cookie?
> 
> If possible to store in database -- any examples available? Google has not been my friend.
>

I don't think your users are especially fickle.  Storing consent client-side is a horrible idea.

Storing consent in a database is described in the shibs docs

Consent configuration:
   https://wiki.shibboleth.net/confluence/x/5oAgAQ

Storage configuration:
   Chttps://wiki.shibboleth.net/confluence/x/lYEgAQ


We don't use consent in production yet.  But in testing the DB method seems to work fine.

Jim