Submitter: Robert Lyon (
Branch:    16.10_STABLE

commit 032b6ba69ec7fc0db1f6a61ec53402c3c1a1cb49
Author: Aaron Wells <>
Date:   Mon Sep 26 15:32:04 2016 +1300

Bug 1620879: Adding webservices to replicate api/mobile functionality.

behatnotneeded: can't test in behat

Change-Id: I9b8cfada9122cafe72afea86f573873b9d781bfb
(cherry picked from commit a617b3c21864aedf1c26f107537da5024a212fb2)

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 forum before editing or unsubscribing it!

  Allow users to self-issue webservice access tokens

Status in Mahara:
  Fix Committed

Bug description:
  For the generation 2 Mahara mobile app ( ), 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

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to