Hi Stefan,
On 28 Mar 2017, at 11:35 AM, Stefan Winter <
stefan...@restena.lu> wrote:
> Hi,
>
> after upgrading from 1.13 to 1.14, copying over all config files, I get server errors with something rather weird in the logs:
>
> [28-Mar-2017 11:20:48 Europe/Luxembourg] PHP Warning: Erroneous data format for unserializing 'SimpleSAML_Session' in /export/hosting/restena/clueless_private/private/simplesamlphp-1.14.11/lib/SimpleSAML/SessionHandlerPHP.php on line 263
> [28-Mar-2017 11:20:48 Europe/Luxembourg] PHP Notice: unserialize(): Error at offset 30 of 4067 bytes in /export/hosting/restena/clueless_private/private/simplesamlphp-1.14.11/lib/SimpleSAML/SessionHandlerPHP.php on line 263
> [28-Mar-2017 11:20:48 Europe/Luxembourg] PHP Notice: Trying to get property of non-object in /export/hosting/restena/clueless_private/private/simplesamlphp-1.14.11/lib/SimpleSAML/Session.php on line 335
> [28-Mar-2017 11:20:48 Europe/Luxembourg] PHP Catchable fatal error: Argument 1 passed to SimpleSAML_Session::load() must be an instance of SimpleSAML_Session, boolean given, called in /export/hosting/restena/clueless_private/private/simplesamlphp-1.14.11/lib/SimpleSAML/Session.php on line 266 and defined in /export/hosting/restena/clueless_private/private/simplesamlphp-1.14.11/lib/SimpleSAML/Session.php on line 378
> [28-Mar-2017 11:20:48 Europe/Luxembourg] PHP Catchable fatal error: Argument 1 passed to SimpleSAML_Session::load() must be an instance of SimpleSAML_Session, boolean given, called in /export/hosting/restena/clueless_private/private/simplesamlphp-1.14.11/lib/SimpleSAML/Session.php on line 266 and defined in /export/hosting/restena/clueless_private/private/simplesamlphp-1.14.11/lib/SimpleSAML/Session.php on line 378
>
> So... something went wrong during an unserialize() ? That doesn't look like something I could have done wrong myself.
>
> The setup is mildly special in that the www subfolder is in the webroot while the rest of the installation is outside; I have adapted the "autoloader" loading (line 32) for it to find itself.
>
> It used to be working like that for many SSP versions, so I don't suspect the error to be there?
That’s “normal”.
In the latest versions of SimpleSAMLphp we addressed an issue with eduPersonTargetedID. Basically, its value was lost when serializing the session if the value was a NameID (as it should be, on the other hand). This was due to the NameID not being parsed in older versions of the SAML2 library, and therefore an unserializable DOM object being returned. In any case, in order to fix this we had to change slightly the way we serialize the session object (basically, intercept serialization so that we could dump to string any DOM objects, and the other way around). This change had the unwanted side effect of errors like the ones you are seeing.
Luckily, errors are temporary and happen only for those users who already had a session before the update, and then load it again after the update. If I’m not mistaken, the errors do not invalidate the session (so the users shouldn’t note anything), and they should happen only once, as saving the session again will solve the problem.
So to summarize: nothing to worry about.
--
Jaime Pérez
UNINETT / Feide
jaime...@uninett.no
jaime...@protonmail.com
9A08 EA20 E062 70B4 616B 43E3 562A FE3A 6293 62C2
"Two roads diverged in a wood, and I, I took the one less traveled by, and that has made all the difference."
- Robert Frost