Consent Configuration

Jann Malenkoff jannmalenkoff at gmail.com
Wed Jun 15 01:07:35 EDT 2016


I hear you Scott!

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.

On Tue, Jun 14, 2016 at 4:05 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:

> > W.r.t attribute consent -- if we want to preserve information that user
> has
> > previously consented for the attribute's release, and not be asked again
> --
> > after a server restart -- the 'idp.consent.StorageService' has to be in
> the
> > database?
>
> No, not really. Any persistent storage option will survive a restart.
> Cookies are persistent, though of course they can be deleted, and any
> client-side option is per-device. But that's independent of restarting. The
> most common way of deploying uApprove was certainly a database, but
> uApprove got almost no deployment in the US. We took the hint. At least I
> did.
>
> -- Scott
>
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20160614/96038020/attachment.html>


More information about the users mailing list