|Table of Contents|
Avalon as an LTI tool in a LMS
Avalon release 3 introduced Learning Tool Interoperability (LTI) capability. 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. All a user would need to do to access course items is to log into their LMS, click on an external tool link, and then they will be redirected to Avalon. As part of the redirect, avalon gathers course and user information verified by Oauth. Using the course id, avalon customizes the landing page for the user to only show items listed for that course.
Set up Process
Add the LMS as an authentication provider
- :name: Avalon LTI Oauth :provider: :lti :hidden: true :params: :oauth_credentials: key: 'secret'
Configure hash keys
There are more lti configuration options in config/lti.yml, which tells avalon where to look for user, class and lms information in the hash received from the LMS. These are the default values that are hard-coded into our version of the gem omniauth-lti. You'll only need to add the lti.yml if any of these values are different for your LMS. You might want to follow this recipe for choosing values to avoid confusion in the interface.
--- <tool_consumer_instance_guid>: :uid: :user_id :email: :lis_person_contact_email_primary :context_id: :context_id :context_name: :context_label
The next step is to go into your LMS or CMS and create a link to the avalon LTI.
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".
Check the boxes to release the name and email address to the external tool. If these aren't checked, students logging in the first time through sakai will receive an error message.
Canvas allows for the specification of global as well as course-specific LTI providers. From either the Global or the Course Settings, click Apps, then View App Center to reveal the Add New App button.