05 November 2014, 0:20

Hi again

We may have found the issue.  We found in the table 'mhr_auth_remote_user" that we have several entries for many localusr.

When we change the authentification method from authinstance A  to authinstance B for a specific usr from the backoffice, a new entry is created in this table for this user.  The user is now facing difficulties to submit pages from the different moodle platforms. (see screenshot)

If we delete entry with authinstance A, the issue is fixed.

Why does Mahara keep those entries in the db ? is it a bug ? By the way, why localuser isn't  primary key in this table ? 

Emilie

05 November 2014, 3:28

In the meantime, i found this post related to the table 'mhr_auth_remote_user'

https://mahara.org/interaction/forum/topic.php?id=6042

There's a bug opened in the launchpad : https://bugs.launchpad.net/mahara/+bug/1269665 .

Maybe our issue is also linked to this bug : when changing authentification method from the back office, duplicated entries are created for the user in table 'mhr_auth_remote_user'.

We had also some users that were not in this table..

All our users should have the CAS authentification method (parent for all XML-RPC auth methods).

To fix the issue, we dropped the table and insert again all users correctly : (based on Tony Box's mysql query):

INSERT INTO mhr_auth_remote_user (authinstance,remoteusername,localusr)
SELECT authinstance,username,id
FROM mhr_usr
WHERE mhr_usr.authinstance != 1

Now it works fine !

Emilie