mahara-contributors team mailing list archive

[Jürgen Zimmer <625182@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Dear all,

Hi,

I run Mahara 1.2.5 on our Linux server with a MySQL DB and we use Shibboleth authentication.
I believe there is a bug in the library 
   auth/saml/lib.php

because the lastlogin and lastlastlogin entries in the usr table of the DB were always the same for all users. This only occured with SSO. 
I think there was an update done twice and the lastlastlogin was simply overwritten. 
Commenting the lines 224-225 in the file  auth/saml/lib.php solved the issue for me.

           //$user->lastlastlogin = $user->lastlogin;
            //$user->lastlogin = time()
Apparently, the update is already done somwhere else (auth/lib.php ?).
Hope that helps.

best regards 
  Juergen Zimmer

** Affects: mahara
     Importance: Undecided
         Status: New


** Tags: lastlastlogin saml

-- 
lastlastlogin not set correctly in auth/saml/lib.php
https://bugs.launchpad.net/bugs/625182
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.

Status in Mahara ePortfolio: New

Bug description:
Dear all, 

Hi,

I run Mahara 1.2.5 on our Linux server with a MySQL DB and we use Shibboleth authentication.
I believe there is a bug in the library 
   auth/saml/lib.php

because the lastlogin and lastlastlogin entries in the usr table of the DB were always the same for all users. This only occured with SSO. 
I think there was an update done twice and the lastlastlogin was simply overwritten. 
Commenting the lines 224-225 in the file  auth/saml/lib.php solved the issue for me.

           //$user->lastlastlogin = $user->lastlogin;
            //$user->lastlogin = time()
Apparently, the update is already done somwhere else (auth/lib.php ?).
Hope that helps.

best regards 
  Juergen Zimmer