Note:

If you want to create a new page for developers, you should create it on the Moodle Developer Resource site.

MNet Roadmap: Difference between revisions

From MoodleDocs
(New page: ==Changes Penny wants to make for Portfolio API/further Mahara Integration== As mnet evolves and potentially other services are offered than sso and enrolment, and potentially as more app...)
 
No edit summary
 
(9 intermediate revisions by 4 users not shown)
Line 1: Line 1:
==Changes Penny wants to make for Portfolio API/further Mahara Integration==
{{Infobox Project
|name = Mnet Standards Roadmap 2014
|state = Early specification]
|tracker = MDL-40905
|discussion = [https://moodle.org/mod/forum/discuss.php?d=175158 here]
|assignee = many
}}


As mnet evolves and potentially other services are offered than sso and enrolment, and potentially as more applications are written that talk mnet (there was a drupal mnet project, for example), it makes sense to start splitting out what services are offered by each application.  To this end, I propse adding a new table, application2service, which links application to service, and moves the url field from the application table.  It would look like this:




{| border="1" cellpadding="2" cellspacing="0"
Key architectural considerations up for further discussion are:
|-
|'''Field'''
|'''Datatype'''
|'''Comment'''
|-
|id
|integer
|sequence
|-
|applicationid
|integer
|fk to mnet_application
|-
|serviceid
|integer
|fk to mnet_service
|-
|url
|char (255)
|this is to replace application.sso_land_url (application.xmlrpc_server_url should still stay where it is)
|}


I had originally thought about adding publishable and subscribeable fields to this table, but really I think this should be dictated by what the remote hosts offer.  Not convinced on this point yet.
* importing SimpleSAMLphp as a first class addition to Moodle and Mahara to make the process of configuration simpler
* introduction of wizards and automations that hide the complexity of SSO integration configuration


===Common Tasks===


* Deprecation roadmap - figure out the tasks, and milestones required to determine what releases will mark out the deprecations of the existing MNet functionality as the web services and SAML authentication replacement becomes available.
* Standardise on REST + JSON


==Changes Catalyst will be making to improve Moodle/Mahara SSO===
The following task lists are divided by system, but this does not necessarily delineate responsibility.
Nigel todo


==Changes Catalyst want to make longer term===
===Mahara Centred Tasks===
Nigel/Peterb todo
 
* Land the  Web Services plugin in Mahara core
* Include SimpleSAMLphp as first class library
* Connection manager for client connections in web services - ssphp connection wizard,  wizard for inter-Moodle/Mahara connections "just enter URL + Token"
* Migrate MNet functionality to Web Services for Portfolio, account provisioning
* Update Launch block for network servers
 
===Moodle Centred Tasks===
 
* Include SimpleSAMLphp as first class library
* Connection manager for client connections in web services - ssphp connection wizard, wizard for inter-Moodle/Mahara connections "just enter URL + Token"
* Migrate MNet functionality to Web Services for mahara portfolio plugin, assignment plugin, account provisioning
* Assignment plugin was originally proposed to be replaced with LTI based functionality, but a better approach has been suggested using a repository plugin.
* Authentication sources separate from mdl_user table
* Investigate community hubs and MNet use ?
* Launch block replacement for MNet servers jump point

Latest revision as of 09:51, 7 October 2014

Mnet Standards Roadmap 2014
Project state Early specification]
Tracker issue MDL-40905
Discussion here
Assignee many



Key architectural considerations up for further discussion are:

  • importing SimpleSAMLphp as a first class addition to Moodle and Mahara to make the process of configuration simpler
  • introduction of wizards and automations that hide the complexity of SSO integration configuration

Common Tasks

  • Deprecation roadmap - figure out the tasks, and milestones required to determine what releases will mark out the deprecations of the existing MNet functionality as the web services and SAML authentication replacement becomes available.
  • Standardise on REST + JSON

The following task lists are divided by system, but this does not necessarily delineate responsibility.

Mahara Centred Tasks

  • Land the Web Services plugin in Mahara core
  • Include SimpleSAMLphp as first class library
  • Connection manager for client connections in web services - ssphp connection wizard, wizard for inter-Moodle/Mahara connections "just enter URL + Token"
  • Migrate MNet functionality to Web Services for Portfolio, account provisioning
  • Update Launch block for network servers

Moodle Centred Tasks

  • Include SimpleSAMLphp as first class library
  • Connection manager for client connections in web services - ssphp connection wizard, wizard for inter-Moodle/Mahara connections "just enter URL + Token"
  • Migrate MNet functionality to Web Services for mahara portfolio plugin, assignment plugin, account provisioning
  • Assignment plugin was originally proposed to be replaced with LTI based functionality, but a better approach has been suggested using a repository plugin.
  • Authentication sources separate from mdl_user table
  • Investigate community hubs and MNet use ?
  • Launch block replacement for MNet servers jump point
Retrieved from "https://docs.moodle.org/dev/index.php?title=MNet_Roadmap&oldid=46384"
Powered by MediaWiki