In brief
LTI 1.3 standardizes the secure launch of a tool from a learning platform and, with LTI Advantage, certain exchanges such as activities, roles or notes. However, successful integration depends on registration, identifiers, keys, actually activated services, data rules and lifecycle tests. This article does not claim LTI support or 1EdTech certification for Educati.
1. Name the platform, the tool and the use case
The 1EdTech LTI Core specification distinguishes between the platform, which launches the experience, and the external tool. Before any configuration, write the scenario: a teacher adds a resource, a learner launches it, then information possibly returns to the notebook.
This simple sentence avoids three ambiguities: who initiates the launch, what data is needed, and what service is expected after the launch. A connection that opens a page does not automatically imply synchronization of roles, content or results.
2. Check the LTI 1.3 security contract
LTI Advantage implementation guide describes the use of OpenID Connect for launch and OAuth 2.0 with signed tokens for services. The technical team should verify the issuer, client ID, deployment URLs, redirects, expected audiences, and key sets.
Also test for key rotation, unknown ID, incorrect audience, and unsaved redirection. The expected behavior should be an understandable and traceable refusal. Don't copy secrets into tickets, screenshots, or shared documents.
3. Enable only necessary services
LTI Advantage brings together several capabilities. Deep Linking helps a teacher select and insert content; Assignment and Grade Services deals with grade lines and results; Names and Role Provisioning Services exposes members and roles according to the rights granted. The 1EdTech Deep Linking specification shows that this exchange has its own messages and rules.
For each service, document the need, the scopes, the fields transmitted, the direction of the exchange and the behavior in the event of deletion. The useful principle is the least privilege: do not ask for a list of members if the use case does not require it, and do not give a score if no educational rule provides for it.
4. Test the lifecycle, not just the first launch
A pilot should cover adding, teacher launch, learner launch, copying a course, changing roles, deleting an activity, removing the tool and rotating keys. Add errors: timeout, token replayed, service unavailable, note refused or user absent.
LTI Advantage Compliance Guide details the tests associated with the components of the standard. Only products listed according to 1EdTech rules can claim corresponding certification. An internal interoperability test therefore does not authorize Educati or another actor to use this claim.
5. Link the standard to the Educati project
The Educati school management page is used to identify the business paths to connect. The enterprise EdTech architecture grid helps secure master systems, traceability and recovery. These pages do not constitute a statement of LTI support.
Prepare an integration sheet with versions, URLs, non-secret identifiers, services, scopes, data, owners, environments and acceptance criteria. See Educati prices page to open commercial framing and Educati News hub for related guides.
FAQ
Does LTI 1.3 replace all APIs between an LMS and a tool?
No. LTI covers use cases defined by its messages and services. Other institutional exchanges may require another standard or a separate API.
Does an LTI launch mean the notes are in sync?
No. The return of grades depends in particular on the activation of Assignment and Grade Services, the scopes granted and the behavior actually implemented on both sides.
Is Educati LTI 1.3 certified?
This article makes no claims of certification or support. To verify a planned integration, its versions, and its responsibilities, contact Educati and request evidence that matches the specific scenario.
