mahara-contributors team mailing list archive
-
mahara-contributors team
-
Mailing list archive
-
Message #15526
[Bug 802096] Re: Mahoodle login problem
I marked this as "Invalid" because it's not an issue with Mahara, but
the wiki and thus shouldn't show up anywhere in a changelog.
** Changed in: mahara
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/802096
Title:
Mahoodle login problem
Status in Mahara ePortfolio:
Invalid
Bug description:
as per http://mahara.org/interaction/forum/topic.php?id=3762
Here is just the description with the description
The mahara lib/version.php file I have says 1.3.6 though. The moodle's
version.php shows 2.0.2
In Mahara, if the institution has only XMLRC authentication, or
has others but XMLRC is given no parent, then the problem occurs
exactly as I've described (user data transfers to Mahara from Moodle,
but user cannot get passed 'logged out user home' and is never asked
to change password)
However, If I put Internal auth as a parent to XMLRC on the
institution, then I get a go around, by the following odd set of
events occuring:
I click the Mahara link under network servers in Moodle, and get brought to the logged out user home in Mahara
I do nothing in Mahara, and I go back to Moodle, and click the Mahara link again from the network servers block.
This time, I get transferred to the 'change password' page in Mahara and it says on the side (in Mahara) that I am coming in from Moodle.
After submitting the changed password in Mahara, I get transferred once again to the logged out home. But this time, since internal is the auth parent, I can log in with the password that was just set.
No matter which way I order the auths in the institution, the new user from Moodle defaults to Internal Auth. I can log in as admin in Mahara and change the user's auth method. Then with the auth method changed to XMLRC, the user (once logged into Mahara) can jump back and forth between Moodle and Mahara. However, the user still needs to initially log in to Mahara, Moodle still won't send the user straight in.
So, in conclusion, I have a weird go around that my students can
manage to use, with me having to go into each user account and change
the auth method) - but this really does seem like it should be an easy
fix. When porting over through XMLRC, Mahara just seems to be setting
some value incorrectly which is sending the user to the wrong page.
Also, the wantsurl doesn't seem to be getting set, it just shows
wantsurl= with nothing after the '=' in the redirect. And if there's a
place in moodle to set it for the jump, I don't see where.
Of course, maybe it is still something to do with my setup. I have
moodle and mahara on the same server, and I know nothing about
OpenSSL.
Hopefully this detailed description will help someone see what the
problem is.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/802096/+subscriptions
References