...
The following providers are supported out of the box. Included with each is a brief description of how each works, and working examples of some launch data you could use with each provider. Remember that no user specific data is to be included, this is all added automatically. So the launch data you provide can be very minimal.
| Anchor | ||||
|---|---|---|---|---|
|
Standard
This adapter is a no-op, it allows the parameters to pass through untouched. Unless your provider needs specific data, this is the recommended choice.
...
This sends a request to the sample tool hosted by IMS Global. It allows any key, but assumes a secret of 'secret'. You can add any parameters to the launch data and the provider will see them.
| Anchor | ||||
|---|---|---|---|---|
|
Sakai
This adapter processes the launch data so that it is compliant with the format that the Sakai Basic LTI provider expects. Firstly, the endpoint_url parameter is suffixed with the tool_id. Next the context_id is checked to see if it is a ~. If so, an additional parameter is added, ext_sakai_provider_eid with value of the user_id. This tells the Sakai Basic LTI provider that it is to treat the supplied user_id as the eid, ie jsmith26. Ordinary calls expect this to be the actual internal UUID for the user, which is unknown to external applications without a web service call so we use the available data instead. It also signals that the site we are requesting is the user's My Workspace (signalled by the ~) so we are able to render tools from My Workspace if context_id=~.
...
Overall, ensure you have correctly setup the Basic LTI provider in Sakai.
| Anchor | ||||
|---|---|---|---|---|
|
Peoplesoft
This adapter simply uppercases the user_id. This adapter is still in development and may change. We are in the process of developing the Basic LTI provider for Peoplesoft.
...