Transform Learning with a Powerful Enterprise LMS

Learn more
SCORM, xAPI, cmi5 & LTI

LTI 1.3 Explained: How External Tools Plug Into Your LMS

How LTI 1.3 launches a tool from an LMS with OpenID Connect and signed JWTs, what registration and deployment mean, what LTI Advantage adds, and why LTI 1.1 is deprecated.

Learn more about this topic with AI

Gemini opens with the prompt copied - paste it into the chat to start.

Illustration of a tool tile plugging into an LMS socket, representing an LTI 1.3 launch

LTI 1.3 is the 1EdTech standard that lets a learning platform, usually an LMS, launch an external tool and pass along who the user is, which course they are in and what role they have, without the tool keeping its own login. It replaced the shared-secret signing of LTI 1.1 with OpenID Connect and signed JSON Web Tokens. LTI Advantage is the set of services built on top of LTI 1.3: Deep Linking for picking content, Names and Role Provisioning for class rosters, and Assignment and Grade Services for sending scores back to the gradebook.

If you are connecting a publisher's content, a virtual lab, a proctoring service or your own app to an LMS, LTI 1.3 is the default way to do it today. This explainer covers how a launch works, what registration and deployment mean, what LTI Advantage adds, how it differs from LTI 1.1, and where it fits next to SCORM, xAPI and SSO.

Checked against the 1EdTech LTI Core 1.3 specification and LTI Advantage implementation guide, the 1EdTech deprecation notices, and the Moodle 5.3.0 source for mod_lti and enrol_lti (October 2026).

What LTI 1.3 does

LTI defines two roles. The platform is the system that hosts the learner, such as an LMS. The tool is the external application that provides some function: an e-book reader, a coding sandbox, a video service, an assessment engine. A teacher adds the tool to a course, a learner clicks the link, and the tool opens already knowing the learner, the course and the role, so there is no second login and no manual roster upload.

The core specification defines one message type, the resource link launch, LtiResourceLinkRequest. Other message types, such as the deep linking request, are defined in their own specifications. Every launch carries a set of claims: required ones include the message type, the version (1.3.0), the deployment ID, the target link URI, the resource link with a stable id, the user's roles and, unless the launch is anonymous, the user's sub. Optional claims include the course context, custom parameters, the platform details and launch presentation hints. Claims are namespaced by URI, for example https://purl.imsglobal.org/spec/lti/claim/message_type.

How an LTI 1.3 launch works

An LTI 1.3 launch is an OpenID Connect third-party initiated login. The browser moves between the platform and the tool three times:

  1. Login initiation. The platform sends the browser to the tool's login URL with iss (the platform's issuer), login_hint, target_link_uri and, optionally, lti_message_hint, lti_deployment_id and client_id. None of this is trusted yet.
  2. Authentication request. The tool stores a state and a nonce and redirects the browser back to the platform's authorization endpoint with scope=openid, response_type=id_token, response_mode=form_post, prompt=none, its client_id, its redirect_uri and the hints it received.
  3. Launch. The platform checks the request, builds the launch message and posts it to the tool's redirect URI as an id_token: a JWT signed with the platform's private key. The tool fetches the platform's public keys from its JWKS URL, verifies the signature, the issuer, the audience, the expiry and the nonce, checks the state, and only then trusts the claims.

The specification tells the tool to rely on the signed target_link_uri claim, not the unsigned value from step 1, and says that a lti_deployment_id sent at login must match the deployment in the launch. Messages and service calls must use TLS.

In Moodle 5.3 you can see the platform side of this in code: mod/lti/auth.php rejects any request whose scope is not openid or whose response type is not id_token, mod/lti/certs.php publishes the platform keys, and mod/lti/token.php issues access tokens for services.

Registration, deployment and keys

Before any launch, the platform and the tool exchange configuration. Three identifiers matter:

TermWhat it isWho issues it
Issuer (iss)Identifies the platform, usually its base URLPlatform
Client IDThe tool's OAuth 2 client identifier on that platform: one registrationPlatform
Deployment IDThe scope in which the tool is available, such as a whole site or one account; an immutable, case-sensitive string of up to 255 ASCII charactersPlatform

One registration can have several deployments (the multi-tenant model) or exactly one (single-tenant). Tools usually store data per issuer, client ID and deployment ID, so a tool that ignores the deployment ID can mix up customers who share a platform.

Keys are exchanged as JWK Sets. The LTI Advantage implementation guide says JWK Sets are required for platforms as the only supported mechanism, sets a minimum of RS256 with 2048-bit keys, and recommends that tools cache keys and re-fetch when they see an unknown kid. That last point is what makes key rotation painless; a tool that pins one key breaks on the day the platform rotates.

Registration can be manual (copying URLs and IDs between admin screens) or automatic through 1EdTech's Dynamic Registration, which Moodle has supported as a platform since 3.10.

LTI Advantage: the services on top

LTI Advantage extends LTI 1.3 with three specifications. Two are REST services; Deep Linking is a message type.

SpecificationWhat it doesExample
Deep Linking 2.0The teacher opens the tool, picks content, and the tool returns links that the platform turns into course itemsChoosing three chapters from a publisher library in one step
Names and Role Provisioning Services 2.0The tool reads the course roster and roles from the platformA discussion tool pre-creating groups before anyone launches it
Assignment and Grade Services 2.0The tool creates gradebook columns (line items), posts scores and reads resultsA coding sandbox sending a mark to the LMS gradebook

Services use OAuth 2 client credentials: the tool signs a JWT with its own private key, exchanges it at the platform's token endpoint for an access token, and calls the service with that token. Each service has scopes, for example https://purl.imsglobal.org/spec/lti-ags/scope/score for posting scores and https://purl.imsglobal.org/spec/lti-nrps/scope/contextmembership.readonly for reading the roster. The platform admin decides which services each tool may use.

LTI 1.3 vs 1.1

LTI 1.1LTI 1.3 with Advantage
SecurityOAuth 1.0a request signing with a shared key and secretOpenID Connect launch, signed JWTs, OAuth 2 for services, public/private key pairs
SecretsThe same secret on both sidesEach side keeps its private key; public keys are published
GradesBasic Outcomes: a single score per resource link and userAssignment and Grade Services: line items, scores, results
RosterMembership service (NRPS 1.0, now deprecated)Names and Role Provisioning Services 2.0
Content selectionContent-Item messageDeep Linking 2.0
StatusDeprecated by 1EdTechCurrent

1EdTech announced the deprecation of OAuth 1.0a for LTI 1.1 and stopped certifying it from 1 July 2021. Its deprecation schedule for early LTI versions says all support for LTI 1.0, 1.1, 1.1.1, 1.1.2, 1.2 and 2.0 ended on 30 June 2022, and it recommends adopting LTI 1.3 and LTI Advantage. Platforms may still accept 1.1 connections, but for any new integration, build on 1.3.

Where LTI fits next to SCORM, xAPI and SSO

LTI is often confused with content packaging and single sign-on standards. They solve different problems:

  • SCORM and cmi5 package content that runs inside or is launched by the LMS and reports completion to it. With LTI, the content or app stays on the tool's own servers. See our SCORM vs xAPI vs cmi5 comparison for the packaging side, and the eLearning standards guide for how all of them relate.
  • xAPI records learning activity statements in a learning record store. LTI does not track activity in detail; it launches and, with Advantage, returns grades.
  • SAML and OIDC single sign-on log a user into a system. LTI also uses OpenID Connect, but it carries course context and roles from one specific launch, not a general login session. Our SSO with SAML vs OIDC article covers that side.

LTI 1.3 in common LMS platforms

Moodle works in both directions in core. As a platform it uses the External tool activity (mod_lti), with core LTI services for grades and memberships. As a tool it can publish its own courses and activities to other platforms through the "Publish as LTI tool" enrolment method (enrol_lti, with auth_lti). Moodle's documentation for that feature lists Assignment and Grade Services, Names and Role Provisioning Services and Deep Linking, all at version 2.0, and notes that LTI 1.1 and 2.0 have been deprecated.

WordPress LMS plugins are different. We found no LTI implementation in the core code of LearnDash 4.18.0.1, LifterLMS 8.0.1 or Tutor LMS 4.1.3. Launching LTI tools from those sites, or exposing their courses to another LMS, needs a separate plugin or a custom build. If LTI support is a requirement, check it early; our LMS features checklist includes it as an evaluation item.

Practical issues when you build or connect a tool

  • Validate everything in the id_token. Signature, issuer, audience, expiry and nonce, then the deployment ID. Use a maintained JWT library rather than parsing tokens by hand.
  • Store per deployment. Key data by issuer, client ID and deployment ID, and use the resource link id as the stable reference for a placement.
  • Plan for key rotation. Fetch keys from the JWKS URL and refresh on an unknown kid.
  • Watch iframes and cookies. A common failure we see is a tool that keeps its OIDC state in a cookie while running inside the LMS iframe; browsers that restrict cross-site cookies then break the launch. Opening the tool in a new window, or not relying on that cookie, avoids it.
  • Keep server clocks in sync. Tokens carry issued-at and expiry times, so clock drift on either side causes rejected launches.
  • Ask only for the services you need. Platform admins approve scopes; a tool that requests roster access without a reason slows down procurement.

How we can help

We build and debug LTI 1.3 integrations on both sides: connecting third-party tools to Moodle and other platforms, and adding LTI launch and grade return to custom applications and WordPress LMS sites. See our LMS integration services, or get in touch for a quote on your integration.

Frequently asked questions

What is the difference between LTI 1.3 and LTI Advantage?

LTI 1.3 is the core specification: the secure launch from a platform to a tool. LTI Advantage is the package of extra specifications built on it: Deep Linking 2.0, Names and Role Provisioning Services 2.0 and Assignment and Grade Services 2.0.

Is LTI 1.1 still supported?

1EdTech stopped certifying OAuth 1.0a in July 2021 and ended all support for LTI 1.0, 1.1, 1.1.1, 1.1.2, 1.2 and 2.0 on 30 June 2022. Some platforms still accept 1.1 connections, but new integrations should use LTI 1.3.

What is a deployment ID in LTI 1.3?

An identifier the platform issues for the scope in which a tool is available, such as a whole site or one account. It is immutable and up to 255 ASCII characters, and it is sent in every launch so the tool can tell installations apart.

Is LTI the same as single sign-on?

No. LTI uses OpenID Connect for its launch, but each launch carries the course context, role and resource link for one placement. SSO with SAML or OIDC logs a user into a system without that course context.

Does Moodle support LTI 1.3?

Yes. In core, the External tool activity lets Moodle launch LTI 1.3 tools, and the Publish as LTI tool enrolment method lets other platforms launch Moodle courses and activities, with LTI Advantage services.

Free 30-minute consultation

Not sure where to start? Talk to an LMS engineer.

Tell us what platform you run and what you need. You’ll get honest, practical advice - even if the answer is that you don’t need us.

Sources & references

  1. Learning Tools Interoperability Core Specification 1.3 - 1EdTech
  2. LTI Advantage Implementation Guide 1.3 - 1EdTech
  3. Security Update and Deprecation Schedule for Early Versions of LTI - 1EdTech
  4. Deprecation Notice for OAuth 1.0a - 1EdTech
  5. Publish as LTI tool - Moodle HQ
  6. mod/lti/auth.php (Moodle 5.3.0) - Moodle HQ
Add as a preferred source on Google

Add All-in-One LMS as a preferred source to see more of our articles in Google’s Top Stories.

Learn more about this topic with AI

Gemini opens with the prompt copied - paste it into the chat to start.

Keep reading

Before you go - get a free LMS audit

Tell us which LMS you use and what is not working. An engineer replies within one business day.

Choose which optional cookies we may use. You can change this at any time from "Cookie preferences" in the footer. Cookie policy · Privacy policy