Gargamil
commented
6 years ago Overview
- LTI is a protocol for launching an external application from a Learning Management System with single-sign-on and preserves the learning context and user roles within that context.
- LMS can seamlessly integrate an external Application over an unique URL and a shared secret
- By launching the external Application, the corresponding student data will be send over HTTP POST
- Certified Products for LTI (25.04.2018: 297)
Concept
- URL, Key and Secret for a remote Tool will be provided
- A Teacher can add this Tool to their courses by using URL, secret and key
- The Student now can access the remote tool
Privacy
- Different Tool Providers will be given differing levels of trust and hence more or less identifying information will be sent to the Tool Provider.
- Any fields that contain user identifiable information such as the user's name or e-mail address are optional and may or may not be included in launch data
Launch Request
The accessing Tool has to create a launch request and provide the following data:
- user identity
- course information
- role information
- key
- signature
Information are send over HTTP (signed over OAuth).
Become a Provider
- Reference-Implementation, PHP
- Services to implement:
- Consumer Configuration-Management-Tool (for handling e.g. key and secret + more)
- Service to handle income launch-requests. Tasks
- Implementation Guide
Moodle
Supported by moodle as consumer and provider
User Story
As a: Product Owner
I want: to know the expected outcame and work load of the support of the standard LTI
so that: I can decide if we should support this standard.
Acceptance criteria:
Additional info:
see LTI® v1.3
Please tag this issue if you are sure to which tag(s) it belongs.