Consent Form & eduPersonTargetedId

[Joel Levin]

Thanks Scott!

If I understood  correctly - it will be better to go with JPAStorage - this
will take care of both the 'Consent'  and eduPersonTargettedId?


On Thu, Jun 9, 2016 at 11:58 AM, Cantor, Scott <cantor.2 at osu.edu> wrote:

> > - Attribute Release Consent Form - if a user agrees to attributes
> release for
> > an application - can this be store indefinitely (i.e. user is not
> prompted again -
> > even if session expired)?
>
> In memcache? Not unless you never restart it I guess. Memcache is not a
> persistence mechanism, it's just pretending to be one for long enough to
> handle session-oriented data, and our API doesn't distinguish those cases
> so that the code doesn't have to.
>
> > - eduPersonTargettedId - in v3.2.1, there is an option now to store
> values in
> > database (a big help)?
>
> There has always (almost anyway) been such an option.
>
> > If above are stored in the database - would we be better off with
> JPAStorage
> > (instead of memcache)?
>
> Pairwise IDs have to be much more robustly stored than consent records, so
> I would say if you manage to do one, you may as well do the other. The
> problem is getting any of it to work without compromising HA.
>
> -- 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/20160609/0e8a2976/attachment.html>