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

Change how the internal resource code for an LTI2 tool is constructed

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: CLOSED
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 10.0
    • Fix Version/s: 10.1, 11.0
    • Component/s: BasicLTI
    • Labels:
      None
    • 10 status:
      Resolved

      Description

      Currently to construct the internal globally unique tool identifier for an incoming LTI2 tool registration, we make use of the product_family code and the vendor code as well as the resource_type code. This makes no sense as the product_family and vendor codes as indicators of what software is being rung are likely to the the same across lots of intances of a tool hosting container like Tsugi.

      So the new tool registration will be based on the

      tool_profile->product_instance->guid

      Which Per the LMS LTI 2.0 spec is "A globally unique identifier for the service provider. As a best practice, this value should match an Internet domain name assigned by ICANN, but any globally unique identifier is acceptable."

      The guid will be concatenated with the resource_type code.

      This will apply to new registrations. Since re-registration is an LTI 2.1 concept it is not yet supported and the primary place this matters is during re-registration.

        Gliffy Diagrams

          Zeplin

            Attachments

              Activity

                People

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

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    Git Integration