Reports until 08:58, Thursday 01 July 2010
Logbook Admin Bug
jonathan.hanks@LIGO.ORG - posted 08:58, Thursday 01 July 2010 - last comment - 15:00, Thursday 01 July 2010(50)
Corey's Author name troubles 
Corey is still having issues with his name not being pre-populated in the author field of an entry.  This does not happen all the time. He reports that it happened again last night/this morning.  One of the details that he gives is that it happened with a browser tab that had been open to the alog for a long period of time.  This may be an issue of the Shibboleth session timing out.  This may be a bad interaction of lazy binding (which allows us to do anonymous read-only access) and the alog.

If this is the case it would explain corey's issue.  There are ways to mitigate this, by extending the session length for Shibboleth, or making the alog more Shibboleth aware.

I will test this on gold, the test alog server.  There I have the freedom to make the session timeout very small without interfering with others.
Comments related to this report
jonathan.hanks@LIGO.ORG - 14:28, Thursday 01 July 2010 (55)
Link 

At 3:00pm Pacific time 1 July 2010 I will restart the Shibboleth daemon
on the alog.  This is an attempt to address the issues the have been
seen by Corey Gray regarding an author field not being filled out.

Restarting the Shibboleth daemon may require you to hit the login button
again.  However it should not damage any posts you are working on.
However please save your posts to a draft just in case.

I will be extending the Shibboleth session time to a large value.  What is happening with Corey is that his Shibboleth session is expiring after 24hrs.  However the alog still has enough information to identify him, so the posts are allowed, but the author name drops out.  This change can be done very quickly, without requiring new code to be written, so we will try this first.

Scott Koranda and myself are curious about how this will work out, ie will having a SP session that is much longer than the IdP session cause any problems.  Interesting times.
jonathan.hanks@LIGO.ORG - 15:00, Thursday 01 July 2010 (56)
Link 

The Shibboleth daemon has been restarted.  This is a test entry.

I realize I restart the wrong config value, the shib daemon was restarted around 3:30 with the proper settings.

If you see a case where the author name is not filled out.  Please fill it in with your ligo.org name (including the @LIGO.ORG) and post (or save to draft) the entry you were working on.  Then logout and log back in.  This problem should not present itself again.  Sorry for the hastle.