Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-44055

Support emerging IMS spec to auto-provision LTI13

    XMLWordPrintable

    Details

    • Type: Feature Request
    • Status: Verified
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 21.0
    • Fix Version/s: 21.0, 22.0 [Tentative]
    • Component/s: BasicLTI
    • Labels:
      None
    • 21 Status:
      Verified
    • Conversion Script Required:
      Yes
    • Test Plan:
      Hide

      A new document has been written to describe the new auto-provisioning process (these URLs will change to sakaiproject/sakai/master once this code is merged).

      https://github.com/csev/sakai/blob/SAK-44055/basiclti/docs/PROVISION.md

      The Tsugi testing document has been updated to reflect this JIRA:

      https://github.com/csev/sakai/blob/SAK-44055/basiclti/docs/TSUGI.md

      This will require updating LTI QA test plans as it replaces one provisioning approach with another.

       

      Show
      A new document has been written to describe the new auto-provisioning process (these URLs will change to sakaiproject/sakai/master once this code is merged). https://github.com/csev/sakai/blob/SAK-44055/basiclti/docs/PROVISION.md The Tsugi testing document has been updated to reflect this JIRA: https://github.com/csev/sakai/blob/SAK-44055/basiclti/docs/TSUGI.md This will require updating LTI QA test plans as it replaces one provisioning approach with another.  

      Description

      This is an under development spec in the IMS LTI working group - it will evolve over time and Sakai will track those changes.

      This JIRA will delete the SAK-44097 feature because once we have a standard way to auto-provision LTI Advantage there is little point to support a non-standard provisioning mechanism for LTI Advantage.

      This was demonstrated to the IMS LTI working group early December 2020.  The following interoperability goals were achieved:

      • The Sakai worked with Tsugi
      • The Sakai implementation worked with Cengage
      • The Moodle implementation worked with Tsugi
      • The Moodle implementation worked with Cengage

      This is enough interoperability to merge the code into master.  As the spec evolves through review and further interoperability testing, there will be new JIRAs filed and the code will evolve along with the spec.

      Eventually the spec will be published and Sakai will need to be certified.

      In the interim, by releasing this as a feature in Sakai, it allows Sakai to be used to test tools that are also developing the specification.

       

       

        Gliffy Diagrams

          Zeplin

            Attachments

              Issue Links

                Activity

                  People

                  Assignee:
                  csev Charles Severance
                  Reporter:
                  csev Charles Severance
                  Votes:
                  0 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                    Dates

                    Created:
                    Updated:
                    Resolved:

                      Git Integration