Never mind... on further testing it actually does work, and does give me the expected result! :) It was actually already written to look up and store your external username in all the different auth instances, store them in JS, and swap them in and out as you switch auth instances.
-- 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/1160093 Title: Don't display a remote username on /admin/users/edit.php if no remote username exists Status in Mahara ePortfolio: In Progress Bug description: Per default, Mahara displays the "Username for external authentication" on the user account admin page no matter whether the account has actually set a remoteuser value or not. This is confusing when you want to check if an auth instance works correctly because you will have to check the database (in 2 different places) or at least do a user report which pulls the remotuser value from the "correct" DB table. Mahara should only display a remoteuser if it really exists. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1160093/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~mahara-contributors Post to : [email protected] Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
