Implementing LTI 1.3

[stephaniegiang]

This summer we implemented LTI 1.1 and 1.0! However, recently IMS Global introduced LTI 1.3 as the new standard. We should think about moving over to LTI 1.3 soon.

Why we should implement LTI 1.3 soon:

• All 1.0/1.1 services will be depreciated by 12/31/2020
• We have to renew our LTI certification each year and renewing 1.0/1.1 is not possible after 12/31/2019
• This gives us a year to implement 1.3 and get certified for this
• LTI deprecation schedule
• Better security, OAuth2 is being used here instead of OAuth (which has been depreciated for a while)

Migration to 1.3:

• Authorization has changed.
• Request variables have been renamed/changed
• Request is different. JWT is being used as well as less nesting
• Documentation on migration

LMSs that implemented LTI 1.3

• Blackboard
• Canvas
• Moodle
• Sakai

Tools that implemented LTI 1.3

• 14 in total
• Major ones: Turnitin, Top hat

Implementation

Authentication

• Both GitHub Classroom and the LMSs will produce private and public keys
• GitHub Classroom will need to share it's public key with the LMSs and vice versa
• When LMSs reaches out to us to authenticate, we will need to know the LMSs public key and share it
• GitHub Classroom can provide a link that has all the info that the LMS need (public key, oauth2 link, roster import endpoint), make on-boarding much easier. All teachers need to do is provide the link to the LMSs

[hanleybrand]

Another benefit is that schools won't need to have that secret membership feature turned on for their instance, since the membership & roles feature is baked in to LTI 1.3

[tgalling]

Brightspace is LTI 1.3 compliant as well - Looking forward to being able to use the membership service.

[samldiop]

Hello, any updates on the timeline on the move to LTI 1.3?