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

Delete tool_public_key and tool_private_key fields from the lti_tool table

    XMLWordPrintable

    Details

    • 21 Status:
      Resolved
    • Test Plan:
      Hide

      You should test LTI in general to make sure there are no regressions.  After the fix - you should be able to look in the database on a fresh install and the columns lti13_tool_public and lti13_tool_private will not be there.

      Show
      You should test LTI in general to make sure there are no regressions.  After the fix - you should be able to look in the database on a fresh install and the columns lti13_tool_public and lti13_tool_private will not be there.

      Description

      Back in ancient history (2 years ago) we thought tools would not be able to mint their own public private pairs so we had LMS's mint them and provide them.

      This was always a very bad idea (sending private keys around) and while the earliest implementations of LTI Advantage in the LMS's supported it - by the time the last LMS (i.e. D2L) implemented LTI Advantage - all the major LMS's insisted that tool produce a keyset URL and had no support for this feature.

      So this is vestigial code and needs to be removed.  SAK-44105 hid them - but this fix will remove them completely.

        Gliffy Diagrams

          Zeplin

            Attachments

              Issue Links

                Activity

                  People

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

                    Dates

                    Created:
                    Updated:
                    Resolved:

                      Git Integration