No flow execution could be found with key 'e1s1'

[Y Levine]

Thanks again Scott!

>> Is it possible to remove DB storage of session .... but maintain the
storage of the attribute release intercept and shibpid
>> (persistentID)?

>Yes, given that they're all configured independently.

With the understood limitations of SLO -- will it further "impede" SLO
w.r.t moving away from sessions in the DB?

Thanks.


On Thu, Aug 24, 2017 at 6:15 AM, Cantor, Scott <cantor.2 at osu.edu> wrote:

> On 8/23/17, 9:39 PM, "users on behalf of Y Levine" <
> users-bounces at shibboleth.net on behalf of ylevine20 at gmail.com> wrote:
>
> > Legal obligation to store for the attribute release intercept records +
> support reasons to store the persistent ID (in shibpid)
>
> There's an audit log of the consent, so I have a hard time believing
> there's any more legally required, but you can find a lawyer to tell you
> anything (which  is why you just find one to tell you that you don't).
>
> Anyway...
>
> > Is it possible to remove DB storage of session .... but maintain the
> storage of the attribute release intercept and shibpid
> > (persistentID)?
>
> Yes, given that they're all configured independently.
>
> -- 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/20170825/a4c74d2e/attachment.html>