Obsolete:MNET 1.0 workplan: Difference between revisions
From MoodleDocs
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
= Work involved = | = Work involved = | ||
== Infrastructure == | |||
* RPC layer | |||
** Pick a library | |||
** Make sure HTTPS support is solid, including handling invalid certs | |||
** Make sure HTTPS-related errors are reported in a useful fashion | |||
** Add msg encryption and signing (at what layer?) | |||
* Revamp Auth into multi-auth | |||
** We will be writing a auth/mnet plugin | |||
* Review SSO plugins infrastructure -- needs some work to support mnet | |||
** Specially logouts | |||
* Fix pending bugs in multi-enrol | |||
** We will be writing enrol/mnet plugin | |||
== Base protocol == | |||
= Older notes = | |||
== Trust and encryption == | == Trust and encryption == | ||
* HTTP client to handle HTTPS correctly, and dealing with self-signed certs in a user-friendly way | * HTTP client to handle HTTPS correctly, and dealing with self-signed certs in a user-friendly way | ||
* Define a simple API to | * Define a simple API to | ||
Revision as of 22:39, 7 August 2006
Work involved
Infrastructure
- RPC layer
- Pick a library
- Make sure HTTPS support is solid, including handling invalid certs
- Make sure HTTPS-related errors are reported in a useful fashion
- Add msg encryption and signing (at what layer?)
- Revamp Auth into multi-auth
- We will be writing a auth/mnet plugin
- Review SSO plugins infrastructure -- needs some work to support mnet
- Specially logouts
- Fix pending bugs in multi-enrol
- We will be writing enrol/mnet plugin
Base protocol
Older notes
Trust and encryption
- HTTP client to handle HTTPS correctly, and dealing with self-signed certs in a user-friendly way
- Define a simple API to
- Publish pub cert
- Publish services offered
- Trigger services offered
- Create "allow users to SSO" service
- Options: users shortlist, remote admin approval
- Requires Auth API work and plugin changes
- Create "allow users to enrol in courses" service
- Options: courses shortlist, remote admin approval
- Requires Enrol API work and plugin changes
User-friendly admin pages
- Establish and manage trust relations
- Open/close services
- Each service with an associated usage report. Examples:
- What remote users are logging in, from where, which remote admin OKd them
- What remote users are enrolled in, from where, which remote admin OKd them
Protocol and services
- TODO
Core Moodle Changes
We will need to
- Review enrolment plugins API -- perhaps bring in some minor changes
- Rework auth plugins API as discussed in the Multi_Authentication plan
