Export Assertions when using ODBC Storage Service

Cantor, Scott cantor.2 at osu.edu
Mon Nov 24 09:25:39 EST 2014

On 11/24/14, 8:56 AM, "olle76" <olle76767676 at gmail.com> wrote:
>We're just about to migrate our services to Microsoft Azure and start 
>multiple Windows server instances (IIS 8). As such, we can no longer store
>sessions in memory (ss:mem), instead each instance have its own installed
>shibboleth SP, configured exactly the same, and using a shared database
>(ss:db) to store sessions. Moving from ss:mem to ss:db works fine to some
>extent, however, it seems we can no longer export assertions.
>First of all, is it possible to export assertions when storing sessions in

The chances that you actually need to export assertions is very small, but 
yes, there's no difference, unless there's a bug. You're welcome to file 
it, but it will be a couple of months before I have any time to look at it 
if you're relying on me to investigate it.

You could start by checking for log warnings, and by examining the content 
of the database after it stores a session. It should have a separate 
record in the table for each assertion it caches, and there's a field in 
the XML in the master session record that tracks the assertion ID(s) in 
the session.

-- Scott

More information about the users mailing list