Announce: Database Backed Storage Service
Paul Hethmon
paul.hethmon at clareitysecurity.com
Wed Jan 8 15:44:09 EST 2014
On 1/8/14 3:06 PM, "Wessel, Keith" <kwessel at illinois.edu> wrote:
>Your code is first creating the session in the database with a
>session-expire_time and a session_id but no login_id since it doesn't
>have one yet. Then, after it has the principal, it tries to update the
>existing session row to add it.
No, it actually does it as a single insert when adding a new entry. An
entry could be updated though as well at a later time for expire time and
such.
There are 2 parts to the storage engine. The first is the actual
Shibboleth plug in, that's the debug statements showing the PrincipalName
correctly. The storage engine then calls the data access layer to persist
the data. After it does so, that's where we are missing the login ID
field, the logging there is showing what the newly created row of data
looks like afterward.
To me it looks like the object from Shib is correct. When it is persisted
to the DB, something is preventing it from writing the login ID column
value.
Paul
More information about the users
mailing list