Feature Wiki
Tabs
LTI
Page Overview
[Hide]- 1 General
- 1.1 Core Concept of LTI
- 1.1.1 LTI Tool Consumer
- 1.1.2 LTI Tool Provider
- 1.1.3 Institutional Benefits
- 1.2 Trust Between Independent Systems
- 1.3 Controlled Data Sharing
- 1.4 Privacy-Aware User Identification
- 1.4.1 LTI 1.1 is based on
- 1.4.2 LTI 1.1 supports
- 1.4.3 Limitations of LTI 1.1
- 1.5 LTI 1.3 is built on
- 1.6 Authentication and Security Improvements
- 1.7 Privacy and Data Protection
- 1.8 LTI Advantage: Modular Architecture
- 1.1 Core Concept of LTI
- 2 Projects
- 3 Suggested Features
- 4 Accepted Features
- 5 Scheduled Features
- 6 Redundant and Rejected Feature Requests
1 General
Maintainer and Tester
- LTI Provider
- Authority to Sign off on Conceptual Changes: sergiosantiago02
- Authority to Sign off on Code Changes: Zallax, sdiaz, smeyer, sergiosantiago02
- Authority to Curate Test Cases: jcop
- Authority to (De-)Assign Authorities: jcop
- Assignee for Security Reports: jcop
- Assignee for Security Issues: jcop
- Unit-specific Guidelines, Rules, and Regulations: LINK MISSING
- LTI Consumer
- Authority to Sign off on Conceptual Changes: sergiosantiago02
- Authority to Sign off on Code Changes: Zallax, sdiaz, sergiosantiago02
- Authority to Curate Test Cases: jcop
- Authority to (De-)Assign Authorities: jcop
- Assignee for Security Reports: jcop
- Assignee for Security Issues: jcop
- Unit-specific Guidelines, Rules, and Regulations: LINK MISSING
Information
Roadmap
Short Term
- Improve the robustness and consistency of Learning Progress data transmission in LTI 1.3.
- Implement LTI 1.3 Dynamic Registration to simplify the setup of external tools and ensure more reliable and standards-compliant integration workflows.
- Introduce support for LTI Deep Linking to simplify the selection and configuration of external learning resources directly within ILIAS.
- Fix issues related to Learning Progress tracking and status updates to ensure accurate and consistent reporting.
Mid Term
- Update existing forms to use the new ILIAS form framework for improved usability, consistency, and maintainability.
Long Term
- Introduce support for the LTI 1.3 Advanced Grading Service to enable more flexible and detailed assessment reporting between ILIAS and external tools.
- Apply for official LTI certification to ensure that ILIAS fully complies with IMS Global standards and guarantees interoperability with certified external tools.
- Create comprehensive user and technical documentation for LTI integration to support administrators, developers, and end users in setup and usage.
Roadmap
Short Term
- Improve the robustness and consistency of Learning Progress data transmission in LTI 1.3.
- Implement LTI 1.3 Dynamic Registration to simplify the setup of external tools and ensure more reliable and standards-compliant integration workflows.
- Fix the LTI 1.1 event listener to ensure Learning Progress data is transmitted immediately after updates.
- Introduce support for LTI Deep Linking to simplify the selection and configuration of external learning resources directly within ILIAS.
Mid Term
- Update existing forms to use the new ILIAS form framework for improved usability, consistency, and maintainability.
Long Term
- Introduce support for the LTI 1.3 Advanced Grading Service to enable more flexible and detailed assessment reporting between ILIAS and external tools.
- Apply for official LTI certification to ensure that ILIAS fully complies with IMS Global standards and guarantees interoperability with certified external tools.
- Create comprehensive user and technical documentation for LTI integration to support administrators, developers, and end users in setup and usage.
Learning Tools Interoperability (LTI) is an open interoperability standard that enables Learning Management Systems (LMS) to integrate external learning applications in a secure, standardized, and seamless way. Its main purpose is to allow institutions to extend the functionality of their LMS without custom integrations or duplicated user management.
LTI allows learners and instructors to access third-party tools directly from within their courses, using a single login and a consistent user experience. This makes it possible to combine the strengths of different educational platforms while keeping the LMS as the central learning environment.
The LTI standard is developed and maintained by 1EdTech Consortium (formerly IMS Global), an international organization that defines interoperability standards for digital learning ecosystems.
1.1 Core Concept of LTI
At its core, Learning Tools Interoperability (LTI) defines a standardized way for two independent systems to work together while keeping their responsibilities clearly separated. Instead of tightly coupling platforms through custom integrations, LTI establishes a trust-based relationship between a learning platform and an external tool.
1.1.1 LTI Tool Consumer
The LTI Tool Consumer is the system that initiates the interaction. This role is typically fulfilled by a Learning Management System (LMS) such as ILIAS.
The Tool Consumer is responsible for:
- Authenticating the user
- Managing courses, roles, and permissions
- Initiating the launch of external tools
- Providing contextual information about the learning environment
In other words, the LMS remains the central authority for user identity, course structure, and access control.
1.1.2 LTI Tool Provider
The LTI Tool Provider is the external application or service that delivers a specific learning function. Examples include assessment systems, virtual labs, coding environments, or multimedia platforms.
The Tool Provider is responsible for:
- Receiving and validating LTI launch requests
- Providing the learning functionality
- Adapting its behavior based on the received context
- Optionally reporting outcomes (such as grades or progress) back to the LMS
The external tool does not manage users or courses independently; instead, it relies on the LMS for contextual and authorization information.
Modern digital learning environments often rely on multiple specialized tools: assessment platforms, video services, programming environments, simulations, plagiarism detection tools, and analytics dashboards. Without a standard like LTI, integrating these tools would require:
- Custom development for each LMS
- Separate user accounts and logins
- Manual synchronization of courses, users, and grades
- Increased maintenance and security risks
LTI addresses these challenges by defining a common protocol that both LMS platforms and external tools can implement. Once a tool supports LTI, it can be connected to any compliant LMS with minimal configuration effort.
1.1.3 Institutional Benefits
From an institutional perspective, LTI’s security and privacy model provides:
- Centralized control over user data
- Reduced risk of data leaks
- Easier compliance with legal and regulatory requirements
- Confidence when integrating third-party tools
Security and privacy are core design principles of Learning Tools Interoperability (LTI). Because LTI enables communication between independent systems operated by different organizations, it must ensure that data exchanges are trustworthy, protected against misuse, and aligned with institutional privacy requirements.
LTI achieves this through a combination of authentication, authorization, data integrity mechanisms, and controlled data sharing policies.
1.2 Trust Between Independent Systems
At the heart of LTI is a trust relationship between the Learning Management System (LMS) and the external tool provider. Before any interaction takes place, both systems are configured to recognize each other as trusted parties.
This trust relationship ensures that:
- Only approved LMS platforms can launch a specific tool
- External tools cannot be accessed arbitrarily
- Communication occurs only between known and authorized systems
Once trust is established, LTI enforces security on every launch and service request.
1.3 Controlled Data Sharing
LTI follows the principle of data minimization: external tools receive only the information that is necessary to provide their functionality.
Institutions can control:
- Which user attributes are shared (e.g., name, email, identifiers)
- Whether identifiers are persistent or context-specific
- Which services a tool is allowed to access
This ensures that personal data is not shared unnecessarily and remains under institutional control.
1.4 Privacy-Aware User Identification
Rather than requiring full user profiles, LTI allows LMS platforms to provide:
- Pseudonymous user identifiers
- Context-specific identifiers unique to a course or activity
This approach allows tools to track user progress and outcomes without exposing personally identifiable information, supporting compliance with privacy and data protection policies.
Since its introduction, Learning Tools Interoperability (LTI) has evolved significantly to address increasing requirements for security, privacy, scalability, and interoperability in digital learning environments. Each new version of the standard reflects lessons learned from real-world deployments and changes in web security best practices.
The early versions of LTI 1.1, were designed to provide a simple and lightweight integration mechanism between Learning Management Systems and external learning tools.
These versions are still widely deployed and supported by many LMS platforms and tools due to their long-standing adoption.
1.4.1 LTI 1.1 is based on
- OAuth 1.0 for request signing and authentication
- HTTP POST-based launch requests
- Shared secrets exchanged during tool registration
In this model, the LMS signs each launch request using a shared key and secret. The external tool validates the signature to confirm that the request originates from a trusted LMS and has not been altered.
1.4.2 LTI 1.1 supports
- Basic tool launch from within the LMS
- Transmission of user identity and role information
- Course and activity context
- Optional outcome services, such as grade return to the LMS
For many years, these features were sufficient to support common use cases such as external quizzes, assignments, and content delivery.
1.4.3 Limitations of LTI 1.1
- Security Constraints
- OAuth 1.0 is considered outdated and complex to implement correctly
- Shared secrets must be stored securely on both sides
- No standardized token-based session management
- Privacy Limitations
- Limited control over which user data is shared
- No fine-grained consent or scope-based permissions
- User identifiers are often static across contexts
- Scalability and Maintainability
- Tool registration and configuration are largely manual
- Limited support for dynamic content selection
- Extensions are often vendor-specific rather than standardized
LTI 1.3 represents a fundamental redesign of the LTI standard. Rather than extending earlier versions, it introduces a modern security architecture aligned with widely adopted web standards.
1.5 LTI 1.3 is built on
- OAuth 2.0
- OpenID Connect (OIDC)
- JSON Web Tokens (JWT)
This change significantly improves security, flexibility, and interoperability.
1.6 Authentication and Security Improvements
1.6.1 LTI 1.3 replaces shared secrets with
- Public/private key cryptography
- Short-lived, signed tokens
- Strong client authentication
Benefits:
- Reduced risk of credential leakage
- Protection against replay attacks
- Clear trust relationships between LMS and tools
- Easier key rotation and lifecycle management
This aligns LTI with modern identity and access management practices used across the web.
1.7 Privacy and Data Protection
LTI 1.3 introduces scope-based data sharing, meaning that:
- Tools only receive the data they explicitly request
- LMS platforms control which services and information are exposed
- User identifiers can be context-specific or pseudonymous
This design supports compliance with privacy regulations and institutional data protection policies.
1.8 LTI Advantage: Modular Architecture
LTI 1.3 is often referred to as LTI Advantage, which describes a set of standardized services that can be implemented independently:
- Deep Linking: Allows instructors to browse, select, or configure tool content directly from within the LMS during course setup.
- Assignment and Grade Services: Enables secure transmission of grades and feedback back to the LMS gradebook using standardized APIs.
- Dynamic Registration: Simplifies the process of connecting an external tool to an LMS by automating much of the configuration that was previously done manually.
- Names and Roles Provisioning Services: Allows tools to retrieve course participant lists and roles in a controlled and secure manner.
This modular approach avoids monolithic integrations and allows LMS platforms and tools to support only the services they need.
Name | Scenario | How LTI Is Used | Benefits |
|---|---|---|---|
Online Assessments and Exams | An institution uses a specialized assessment platform for quizzes, exams, or automated grading. | The assessment tool is integrated into the LMS using LTI. Students access exams directly from the course page, complete them within the external tool, and submit their responses. |
|
Programming and Coding Environments | Courses in computer science or data science require interactive coding environments. | An external coding platform is launched via LTI from the course. The tool receives user and course context and provides individualized coding workspaces. |
|
Virtual Labs and Simulations | Science and engineering courses rely on virtual laboratories or simulations that cannot be implemented directly in the LMS. | The simulation tool is embedded into the course via LTI. Students interact with experiments while the tool uses course context to store progress. |
|
Video and Media Platforms | A course uses an external platform for video hosting, streaming, or interactive video content. | Videos and playlists are selected through Deep Linking and embedded directly into course sections. |
|
2 Projects
The following projects are planned or have been realised for this component:
NEW Projects
Ongoing Projects
Projects On-Hold
- …
Completed Projects
3 Suggested Features
In the following list you can add a request for a new feature or pick-up an already suggested feature about that should be decided again. The lists below show existing suggestions and scheduled features of this component.
Ready for Jour fixe
already suggested
- automatic Update of LTI-Consumers
- Complete ILIAS Installation as LTI Tool
- Configurable Learning Progress for Tools supporting Assignment and Grade Services according to LTI 1.3
- Enforcing Guideline for Top Actions
- Improve Feedback if LTI Resource is no longer accessible
- Interface to get all OER LTI Ressources (ILIAS as tool)
- Keep Session of LTI Tool/Provider
- LTI Blog
- LTI Content Page
- LTI Data Collection
- LTI Exercise
- LTI File
- LTI Glossary
- LTI Group
- LTI Learning Sequence
- LTI Media Pool
- LTI Mediacast
- LTI Outcome Improvements
- LTI Page Editor Component without support for Learning Progress
- LTI Study Program
- LTI xAPI/cmi5
- Prevent User Profiles through Object-Related pseudonymization
- Provide Rating for LTI-Consumer
- Provide Rating for LTI-Provider
- Support Assignment and Grade Services for ILIAS as LTI 1.3 Tool
- Support Deep Linking for ILIAS as LTI 1.3 Tool
- Support for Deep Linking as Consumer/Platform
- Support for IMS Common Cartridge
- Take over Description from LTI-Ressource
- Tile View to select LTI-Providers
- Using a remote LTI-Ressource Repository
4 Accepted Features
The following features have been accepted for trunk but are not yet scheduled for a specific ILIAS version.
- …
5 Scheduled Features
The following features have been scheduled / published in ILIAS 12:
The following features have been scheduled / published in ILIAS 11:
The following features have been scheduled / published in ILIAS 10:
- …
The following features have been scheduled / published in ILIAS 9:
- …
The following features have been scheduled / published in ILIAS 8:
The following features have been scheduled / published in ILIAS 7:
- …
The following features have been scheduled / published in ILIAS 6:
The following features have been scheduled / published in ILIAS 5.4:
- …
The following features have been scheduled / published in ILIAS 5.3:
6 Redundant and Rejected Feature Requests
Requests that are redundant (already implemented in other requests)
- …
Rejected Feature Requests
Last edited: Yesterday, 13:04, Santiago, Sergio [sergiosantiago02]