Consent Form & eduPersonTargetedId

[Cantor, Scott]

> - 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