mahara-contributors team mailing list archive

[Mahara Bot <1620879@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://reviews.mahara.org/7096
Committed: https://git.mahara.org/mahara/mahara/commit/75fb4eb6d5331844859a933264642d5730ba9cb5
Submitter: Robert Lyon (robertl@xxxxxxxxxxxxxxx)
Branch:    16.10_STABLE

commit 75fb4eb6d5331844859a933264642d5730ba9cb5
Author: Aaron Wells <aaronw@xxxxxxxxxxxxxxx>
Date:   Mon Sep 26 14:38:23 2016 +1300

Bug 1620879: Combine duplicate "get_allowed_services" method

Two of the server classes had their own implementations of this,
with slightly different logic. Moving it up into the parent class
in order to make sure everything works the same, all the time.

behatnotneeded: Can't test in Behat

Change-Id: I91c205822a18213c475bbef7c784247cebdbd649
(cherry picked from commit ef871685926ce8767aaa0c0e6e94bea6f80e1a3e)

-- 
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/1620879

Title:
  Allow users to self-issue webservice access tokens

Status in Mahara:
  In Progress

Bug description:
  For the generation 2 Mahara mobile app (
  https://github.com/maharaproject/mahara-mobile ), we want users to be
  able to generate the access tokens they need via the app itself,
  rather than the current process where users have to log in to Mahara
  in a web browser, go to their account settings page, scroll to the
  bottom and manually create an access token (typing in its value
  themselves), then launch the mobile app and write that same access
  token into the mobile app.

  Instead, we envision a process the same as the Moodle Mobile app. The
  user is presented with a username/password field, they enter their
  credentials there, and the app then does the dirty work of talking to
  the Mahara server, requesting the access token, and storing it.

  In order to support SSO options, there also needs to be an alternative
  flow, where the app opens an embedded iframe that displays the Mahara
  login form, and returns the access token value back to the app when
  done.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1620879/+subscriptions