12 March 2009, 10:51

Hello

 I have noticed that, when you create a user account manually, Mahara automatically creates a new row  in the autho_remote_user, assigning a remote user name to the user id (local), along with the autho instance for that user.

 Since, for the time being, a user can only use 1 auth instance to log in Mahara, what is the utility of the "auth_remote_user" table?  Do you plan to use this table in future to assign different autho instances to the same user ID ?

  In any case, at the end of each academic year, any scripts for clearing out obsolete users in each institution should also delete the correspondent rows in the auth_remote_user table. Until we can export the work of our students , the script could change the auth instance/s  id's  assigned to each old student to an internal autho instance for a fictious institution,  for instance. 

Regards

12 March 2009, 16:46

Hi. It's used so we can tell the difference between 'bob' from Moodle 1 and 'bob' from Moodle 2. If two Moodles are set up to SSO to a site, and they both have a 'bob' user, we don't want them SSO-ing into the same account!

The user delete code already does the deletion of rows from that table, by the way.