A robust LTI role mapping feature was added for outbound LTI Launches and NRPS calls in

There is no default mapping - it needs to be added to each tool in the Admin UI. Here is the LTI documentation on role mapping:

This Jira will add a default role mapping if no mapping is specified in the tool that will work in most cases.

This also completely updates the role configuration for the !site.template.lti which has not kept up with !site.template.course since it was created in ( inserted in 2012-02-16) - The new approach is to copy role information from !site.template.course and tweak it. As a side note, should we add a Guest role into the !site.template.course ?

Some of the work in is included in this Jira. If I found some portfolioesque cruft in the files being adjusted - I just took it out. As they say in “Office Space” - “we just fixed the glitch - the rest will take care of itself.”

This fix was designed to be back-portable to Sakai-22/21 - but it will require a conversion script - so the back port effort may not be worth it.

Earle - This needs a conversion before you back port it to 23. The lines fro here:

To the end of the file - need to be run before this is back-ported to 23.

This in effect is the first of two modifications. This modification ignores Plus but fixes the core LTI role mapping. A follow on Jira will plug all this mapping nicely into SakaiPlus. I kept the changes separate to allow for back porting of the mapping without pulling all of SakaiPlus into a branch.