mahara-contributors team mailing list archive
-
mahara-contributors team
-
Mailing list archive
-
Message #14998
[Bug 547589] Re: Store jumpurl in application table
Well it's been 5 years since this bug and that bit of code in original
post is still in place.
The storing of jumpurl may still need to go in the database's
application config table - but I can't happening any time soon :)
--
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/547589
Title:
Store jumpurl in application table
Status in Mahara ePortfolio:
Confirmed
Bug description:
We need to know the remote application's jumpurl so we can send the
user there to log in again if necessary.
See auth/xmlrpc/lib.php:
elseif (!$this->parent) {
$this->kill_parent($remoteusername);
// Redirect back to their IDP if they don't have a parent auth method set
// (aka: they can't log in at Mahara's log in form)
$peer = get_peer($this->wwwroot);
// TODO: This should be stored in the application config table
$jumpurl = str_replace('land', 'jump', $peer->application->ssolandurl);
redirect($this->wwwroot . $jumpurl . '?hostwwwroot=' . dropslash(get_config('wwwroot')) . '&wantsurl=' . urlencode($_SERVER['REQUEST_URI']));
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/547589/+subscriptions