Consent Form & eduPersonTargetedId

[Jann Malenkoff]

Hi All:

We have to register attribute consent -- for legal reasons. And have to
store the eduPersonTargettedId for Help Desk look up.

Based on this thread:

-- we can leverage memcache for HA (although we also have a load balancer
-- but may have to restart servers occationally)
-- JPAStorageService for database storage of 'attribute consent' agreements
& eduPersonTargettedId

Although would be great to have no DB dependency - but the call came from
high on up.

Given the above -- are we on an implementation track that is workable?


On Thu, Jun 9, 2016 at 12:14 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:

> > If I understood  correctly - it will be better to go with JPAStorage -
> this will
> > take care of both the 'Consent'  and eduPersonTargettedId?
>
> Persistent ID storage is a dedicated piece of code and doesn't use the
> same code as the JPAStorage plugin. You can use the same database for both
> I would assume.
>
> I'm not advocating either. Databases are almost always a single point of
> failure, and I don't use one with my IdP. The IdP comes with the
> configuration I advocate. The fact that it doesn't support consent other
> than per-device is because I value statelessness over virtually every other
> consideration and think it is the best choice for the majority of sites.
>
> -- 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/3c22e646/attachment-0001.html>