Affects Version/s: None
Fix Version/s: 21.0 [Tentative]
Conversion Script Required:Yes
Back in ancient history in between LTI 2.0 and LTI Advantage, the working group came up with the idea to "improve" LTI 1.1 - it never really happened in the market and with LTI Advantage using JWTs there is little benefit in breaking LTI 1.1 by doing SHA256 launches.
So in Sakai-21, unless there is a good reason, support for SHA256 launches will be removed.
It is a pretty simple change - just remove one line from LTIService.java and a few translation strings - and poof! it is gone.
There is no reason to back-port this to Sakai-20.
A conversion script is not essential - but why not drop an unused column in -21 if we can. This parch will remove the field form the UI and launch code - the column would simply be unused going forward.
If you want to see if you have every used SHA256 on any tool eve in the history of your Sakai run this query on your database:
SELECT count( * ) FROM `lti_tools` where sha256 = 1;