LTI 1.3 Advantage, Explained Without the Spec-Speak
July 9, 2026 · 6 min read
What LTI 1.3 Advantage is, in one sentence
LTI 1.3 lets a tool launch securely from inside an LMS and then talk back to it through three named services: rosters, grades, and content. That's the whole idea. The spec is dense; the job it does is simple, and you can understand it by following one grade from a quiz back to a gradebook.
LTI is the standard, stewarded by 1EdTech, that connects a learning tool to a platform. Version 1.1 signed its messages with OAuth 1.0 shared secrets, which aged badly. 1.3 rebuilt the security on OpenID Connect and signed JWTs, so the platform and tool verify each other with proper keys instead of a secret pasted into two config screens. "Advantage" is the set of services layered on top of that launch. (1EdTech's LTI Advantage overview)
Follow one grade home
A student opens a quiz tool from a course. Here's what the three services are actually doing behind that click:
- The launch (secure). The LMS sends a signed OpenID Connect request; the tool verifies it and knows which course, which user, and what role, without the student logging in again.
- Names and Role Provisioning (the roster). The tool asks the platform for the course roster, so it knows who the learners are and who's the instructor, without you uploading a CSV.
- Assignment and Grade Services (the grade home). The student finishes; the tool posts the score back to a line item in the gradebook. That's the grade finding its way home.
- Deep Linking (the content). When an instructor adds the tool to a module, Deep Linking lets them pick the specific resource and hands the platform a link back to it.
| Service | Plain-English job | The question it answers |
|---|---|---|
| OIDC launch | Prove who's launching, securely | "Is this really that student in that course?" |
| Names & Role Provisioning | Fetch the roster | "Who's in this course, and who teaches it?" |
| Assignment & Grade Services | Send scores back | "Where does this grade go?" |
| Deep Linking | Place specific content | "Which resource did the instructor mean?" |
The part that bites in practice
Every one of those services is a separate contract to test. A launch that works doesn't mean grades pass back, and roster access doesn't mean deep linking is configured. I've watched a term start with a tool that launched perfectly and silently dropped every grade, because AGS was never wired to a line item. Test the launch, the roster fetch, and the passback as three different things, with a real instructor's assignment, not just an API call that returns 200.
Honest caveat: 1.3 is more setup than 1.1. Key registration, an OIDC dance, per-deployment configuration. That's the cost of not signing sensitive traffic with a shared secret, and it's worth paying. If you're still on 1.1, the practical migration guide walks the actual steps, and the LTI migration checklist inside a platform move puts it in sequence. For the sign-in layer underneath all this, SSO options for learning platforms covers the identity side, and custom LMS development treats each LTI service as its own tested contract.
Written by Choaib Mouhrach
Founder & Senior Software Engineer
I design and build custom learning platforms for organizations with complex training and certification workflows. Instead of stitching together plugins and third-party tools, I create systems tailored to how each business operates, reducing administrative overhead while improving the learner experience.
Your learning product deserves its own platform.
If you want to deliver a learning experience built around your product, your learners, and your goals, you are in the right place. We build platforms that give you the control and flexibility to grow without limits.