Data is imported from Moodle to Mahara in two circumstances:
This is the behavior I have observed for existing Mahara accounts and Moodle network:
1) user auth method: internal SSO from Moodle => new account
2) user auth method: XMLRPC no parent SSO from Moodle only, no Mahara sign in
3) user auth method: XMLRPC internal parent SSO from Moodle, Mahara sign in
The last is the behavior I am looking for.
Out of curiosity, will it be importing profile information from the Moodle site for existing users?
Thanks
If you did that, it would tell Mahara that users coming from the Moodle are the same as those users using LDAP. It might be the solution you're looking for, though I'd definitely try it out in a staging environment first.
If that worked, then you'd be affected by this bug - if users logged into the Mahara first, then logged into Mahara through Moodle, they'd get a separate account. But, you could fix that by turning on the $cfg->usersuniquebyusername setting as both sides for you are using LDAP. That's probably more information than you need right now though!
]]>We are experiencing the same thing. We have been using Mahara for over a year now. Until recently we have had some software program limitations that have prevented us from doing the Mahoodle integration. We were forced to do independent logins and load our users into both Moodle and Mahara separately. These limitations have been lifted and we'd like to do the integration.
However, we have 2-3 years of users already entered in our Mahara set up with a significant amount of uploads and views. I have tried to run the SSO once already only to have the double entry bug pop up and cut that plan short. Moving forward on a fix would be very useful.
Thanks
The solution in the meantime is to ensure people come in through the Moodle first, which you might be able to arrange with appropriate social engineering.