...
- The required logic for the Sakai Basic LTI provider was added in version 1.4 . This is shipped with Sakai 2.9 but Basic LTI is also compatible with earlier versions of Sakai right back to 2.6, so and ported back to 1.3. So if you are using an older version of Basic LTI you will need to upgrade the Sakai Basic LTI provider to at least 1.3. If you are using Sakai 2.6, there is a patch included in the source tag of Basic LTI that you need to apply as there are some minor modifications in order to get it runningBasic LTI 1.3 running in Sakai 2.6 (there are a couple of API changes).
- You should also enable the highly trusted consumers setting in sakai.properties. This allows the user_id and context_id to be used by the provider as-is. Under the standard configuration, the Sakai Basic LTI provider will prefix the incoming user_id and context_id, and create a new user account and site. This limits the level of integration possible as many users will have existing sites and content that can be reused outside of Sakai. You need to set the following property to allow the values to passthrough without this prefixing occurring:
Code Block basiclti.provider.highly.trusted.consumers=my.consumer.key.here
- If enabling highly trusted consumers (recommended) it assumes the username of users in both uPortal and Sakai are identical (e.g. jsmith26 in both systems).
- The tool_id you can use is dictated by the list of allowed tools in sakai.properties.
...