Announce: Database Backed Storage Service

[Wessel, Keith]

Paul,

We're finally getting ready to put the database stored session code in production next week, insufficient load testing held us up longer than we'd hoped.

I do need to reserect this old thread once more, though. I ran into one little issue. Looking back at our database, I see a hand full of rows where the session_expire_time is null. Seems these are perhaps insignificant. But before I jump to conclusions, have you seen this? Is it a sign of a problem? And if it isn't, can we add to our stored procedure that deletes orphaned rows? Right now, it deletes orphaned rows for sessions that have expired. Can it also delete orphaned rows where the session_expire_time is null? Or do we need to be smarter and delete rows where the expire time is null and the create date is significantly in the past?

Thanks,
Keith


-----Original Message-----
From: Wessel, Keith 
Sent: Monday, October 21, 2013 10:15 AM
To: Shib Users
Subject: RE: Announce: Database Backed Storage Service

Perfect. Thanks.

Keith


-----Original Message-----
From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net] On Behalf Of Paul Hethmon
Sent: Monday, October 21, 2013 10:06 AM
To: Shib Users
Subject: Re: Announce: Database Backed Storage Service

Yep, that's all it does. The table has a column for session expire time, so it's just delete any where that time has passed, padding it a bit. So something like delete all rows where expire time is more than an hour old.

Paul

On 10/21/13 10:56 AM, "Wessel, Keith" <kwessel at illinois.edu> wrote:

>Does your cleanup job just delete rows with a modify date older than 
>the max IDP session lifetime or something along those lines?
>

--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net