Writing still in progress
Avalon as a LTI tool in a LMS
The purpose of setting Avalon up as an LTI tool in an LMS is to offer course-specific access and customized content verified by the LMS.
Set up Process
Add the LMS as an authentication provider.
The authentication settings for LTI are added to config/authentication.yml with the other authentication providers. A new parameter called "hidden" was added to keep the LTI provider from showing up at the log in screen. Here is an example LTI authentication config block:
- :name: Avalon LTI Oauth :provider: :lti :hidden: true :params: :oauth_credentials: key: 'secret'
The file config/lti.yml tells avalon where to look for user, class and lms information in the hash received from LMS. These are the default values that are hard-coded into our version of the gem omniauth-lti. You'll only need the lti.yml if any of these values are different for your LMS.
--- <lms guid>: :uid: :user_id :email: :lis_person_contact_email_primary :context_id: :context_id :context_name: :context_label
LMS/CMS Specific Setup Instructions
Sakai
To add an external tool to a course, go to site setup on the sidebar then check off the box for one of the external tools. We already named one "Avalon".
It will then show up in the side bar.
Click on it and select the edit button in the upper left hand corner. We used the following settings: