Manually force Shibboleth SP to expire/invalidate all sessions

[Tom Noonan]

I'm not using memcached.  I think there is some confusion with another
thread.

--Tom Noonan II

On Wed, Feb 21, 2018 at 11:18 AM, Peter Schober <peter.schober at univie.ac.at>
wrote:

> * Tom Noonan <tom at joinroot.com> [2018-02-21 16:53]:
> > >I'd still be interested in your comments about this approach:
> > > replacing your memcached instances with Couchbase Server?
> > > https://www.couchbase.com/memcached
> >
> > I guess I don't understand the approach and therefore the question?
>
> You said you were using memcached for sessions but memcached does not
> support replication, so it's unusable for your purposes, even though
> the SP supports the protocol for session storage.
>
> So I suggested to use a replacement for the memcached server --
> specifically Couchbase Server -- that *does* support replication and
> uses the *same* *wire* *protocol* as memcached.
>
> Seemed to me that would provide you with clustered sessions on the
> server-side, using existing and Free/Libre/Open Source software (Shib
> SP with memcache protocol support as client, couchbase server as
> server) and somewhat established protocols (memcache).
>
> The server also happens to have an API which may help achieve your
> goal of terminating sessions administratively, I would think.
>
> Is the suggestion sufficiently clear now?
>
> -peter
> --
> For Consortium Member technical support, see https://wiki.shibboleth.net/
> confluence/x/coFAAg
> 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/20180221/5713aabf/attachment.html>