...
- 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:
Code Block - :name: Avalon LTI Oauth :provider: :lti :hidden: true :params: :oauth_credentials: key: 'secret'
Match the key:'secret' pair to the LMS External tool configuration and the user should be able to log in through the LMS.
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.
Code Block --- <lms guid>: :uid: :user_id :email: :lis_person_contact_email_primary :context_id: :context_id :context_name: :context_label
Anchor | ||||
---|---|---|---|---|
|
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".
...