LTI 1.3 Integrations
Basics
Important terms in LTI terminology:
- Platform (corresponds to client): the LMS into which the external content is integrated.
- Tool (corresponds to host): the LMS or application that makes content available to others.
OpenOlat can take on both roles: As a tool, OpenOlat provides a course or a group to another LMS. As a platform, OpenOlat displays the content of an external tool in the course, through the course element "LTI Page".
Activate LTI
Administrators activate LTI in the system administration under Administration > External tools > LTI, tab "Configuration". The checkbox "Enabled" next to the field Module "LTI 1.3" is at the very top. Only then can LTI connections be set up.
Once enabled, the tab shows two further fields:
| Field | Note |
|---|---|
| Platform ISS | The URL with which OpenOlat identifies itself to external systems. Provided by OpenOlat, read-only. The default is the domain of the instance. |
| Organisation | The organisation to which OpenOlat assigns the user accounts that are newly created on access from an external platform. Without a selection, the default organisation applies. |
The page LTI has four tabs: "Configuration" for the basic settings on this page, "External platforms" for OpenOlat as tool, "External tools" for OpenOlat as platform and "Role mapping" for the assignment of OpenOlat roles to LTI roles. The detail pages are linked below.
Deployments
What is a deployment?
On the platform side, the deployment of a tool determines the extent to which the platform makes the tool available:
- Use in a single course
- Use in the entire system
- Use only for the current context
- Use generally enabled (also for future contexts)
On the tool side, the counterpart is called LTI share: if OpenOlat is the tool, an LTI share releases exactly one course or one group for an external platform. In the user interface it is called deployment, for example in the button "Add deployment".
Does one deployment ID apply to several courses?
Yes, if OpenOlat is the tool. An external platform often sends the same deployment ID for several courses, namely when it runs the tool as a shared deployment. OpenOlat itself does this as a platform with the option "With shared deployment" and when an "LTI page" course element is copied, see Global or local deployment. Enter this deployment ID in the LTI share of every course and every group the platform should reach. It only has to be unique per platform and course, or per platform and group. OpenOlat recognizes which course to open from the address the platform sends with the call: One deployment ID for several courses
Who can add deployments?
Administrators determine in the tab "Configuration" under Administration > External tools > LTI who is allowed to add deployments. The setting exists separately for courses and for groups.
Course
- "Role can add deployment": Administrators are always allowed to. In addition, learning resource managers can be enabled.
- "Owner with author role can add deployment": "Activate for all courses" or "Must be activated per course".
Group
- "Role can add deployment": Administrators are always allowed to. In addition, group managers can be enabled.
- "Group coach with author role can add deployment": "Activate for all groups" or "Must be activated per group".
Further information
Mentioned on this page
LTI - External tools >
Configure LTI access to a course >
Further reading
Learning Tools Interoperability Core Specification (IMS Global Learning Consortium) >
LTI - External Platforms >
LTI - Deep Linking >
LTI - Role mapping >
Course element "LTI Page" >
Configure LTI access to a group >