Overview

As part of the LMS Connect offering, your application can be integrated into a district's LMS as an LTI 1.3-compliant SSO link. To get started, simply ensure you have a functioning Clever District SSO integration—we'll handle the rest!

Launch data format

LTI 1.3 launches use OpenID Connect and send your application a signed ID token in JWT format. Your application should validate the token and use the launch claims to identify the user and LMS context.

The launch can include user identity, role, and context about where the launch originated in the LMS, such as the course or section context. Use that context to route the user into the correct course-level experience in your application.

Course-level routing

LTI 1.3 launches are context-aware. When a user launches your app from a course in the LMS, your application should use the launch context to map that LMS course or section to the corresponding course, class, or section in your system.

If you already have a mapping for the LMS context, route the user directly into that course-level view. If your application cannot map the launch context to an existing course, show a setup or matching flow instead of asking the user to choose from an unrelated list of courses.

📘

LTI launch context is not Deep Linking

A course-level LTI launch is different from LTI Deep Linking, which is used to select or embed specific content, resources, or assignments in the LMS. Do not rely on Deep Linking behavior unless Clever has explicitly confirmed that it is supported for your LMS Connect implementation.

To learn more about how districts can set up LTI SSO with your application in their LMS, check out this Help Center article.

☝️

Supported LMSs

Please note that LTI 1.3 SSO is currently only supported for Canvas and Schoology.