Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Deprecate and Remove support for IMS LTI 2.0

Description

At this point, all the major vendors that support LTI 2.0 have quietly decided to move away from LTI 2.0 and towards LTI 1.3 and ContentItem and follow-ons.

LTI 2.0 has a few good features and a lot of bad ideas.  Sakai's LTI 2.0 (and almost LTI 2.1) is one of the best in the industry and one of only two certified LTI 2.0 LMS's.

But even with all that it is a bunch of code that if never used is a liability for security and maintenance - and as new features like LTI 1.3, its services, and new follow-on specs emerge - it is nice to clean up a large amount of code to make space for new stuff.

So at this point LTI 2.0 is deprecated in Sakai 19 and will be removed by the following release of Sakai unless something changes in the marketplace.

If you have any concerns - or tools that require LTI 2.0 - please note them in this JIRA.

Attachments

1
  • 28 Aug 2018, 10:15 PM

depends on

is related to

Activity

Charles R Severance July 25, 2019 at 3:35 PM
Edited

This feature will no longer exist in Sakai-20 and later as LTI 2.0 will be completely deleted when https://sakaiproject.atlassian.net/browse/SAK-41789#icft=SAK-41789 is finished.

Charles R Severance August 28, 2018 at 10:30 AM

Wow - that is kind of cool in a way.  Nothing in Sakai-19 will stop existing installed LTI 2.0 tools from working.   It will just hide the admin UI by default.

Sam Ottenhoff August 28, 2018 at 10:18 AM

Okay, this makes sense to me. PollEverywhere is the most recent client request we had where they only supported LTI 2.0. Obviously they have no choice but to change as the market has changed.

Matthew Jones June 11, 2018 at 1:09 PM

I'm going to make this a blocker for 19 for now as it's something we'd want. We can bump it back later if desired.

Fixed

Details

Priority

Affects versions

Fix versions

Components

Assignee

Reporter

Labels

Property addition/change required

Yes

Created May 31, 2018 at 8:52 AM
Updated April 20, 2022 at 10:23 PM
Resolved August 29, 2018 at 8:09 AM

Flag notifications