mahara-contributors team mailing list archive

[Mahara Bot <1620879@xxxxxxxxxxxxxxxxxx>]

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

commit ecc2b8daa129c946ae26cf7df3c83418c4f8c17f
Author: Aaron Wells <aaronw@xxxxxxxxxxxxxxx>
Date:   Mon Sep 26 14:16:41 2016 +1300

Bug 1620879: Changes to service groups to facilitate automation

- Adding "shortname" field to service groups
- Marking plugin-created service groups, as the ones that have
a "component" field. Make the function list for plugin-created
service groups not editable by users.
- Since users may have already edited the old "sample" service
groups, removing the "component" value from those.
- And, to avoid trouble going forward, preventing the install
of the sample service groups on new installations

behatnotneeded: Tests to be written later

Change-Id: I23c781d6f2bbf689c12de30a67882bf3f1f4aff9
(cherry picked from commit d159aaf425c9453a1d25720eace96f48a2b62d47)

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