![]() why: * LTI 1.1 tools launching from this placement receive the `ext_lti_student_id` launch parameter that corresponds to the student from which the tool was launched * this provides parity for LTI 1.3 tools to receive a similar parameter, `https://www.instructure.com/lti_student_id` closes INTEROP-8058 flag=none test plan: * install a 1.3 tool with the student_context_card placement enabled * Course -> People -> click on a Student * a card will slide out from the right side, and will have a button to launch the 1.3 tool * launch the tool * scroll to the bottom of the decoded id_token * the lti_student_id custom claim should be present and match the id of the student you clicked on * bonus: * change the id in the URL to a non-student - it should fail * change the id to a non-number like SQL injection - it should fail * remove the `&student_id=1` query param entirely - the launch should succeed, but not include the lti_student_id claim * extra bonus: * test this with a 1.1 tool to confirm it's still working as intended Change-Id: Ie3aeebb549c14b978fe84e28748275478685fba4 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/335539 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Paul Gray <paul.gray@instructure.com> QA-Review: Paul Gray <paul.gray@instructure.com> Product-Review: Alexis Nast <alexis.nast@instructure.com> |
||
---|---|---|
.. | ||
lib | ||
spec | ||
.rspec | ||
Gemfile | ||
Gemfile.lock | ||
LICENSE.txt | ||
README.md | ||
Rakefile | ||
lti_outbound.gemspec | ||
test.sh |
README.md
LtiOutbound
TODO: Write a gem description
Installation
Add this line to your application's Gemfile:
gem 'lti_outbound'
And then execute:
$ bundle
Or install it yourself as:
$ gem install lti_outbound
Usage
TODO: Write usage instructions here
Contributing
- Fork it ( http://github.com//lti_outbound/fork )
- Create your feature branch (
git checkout -b my-new-feature
) - Commit your changes (
git commit -am 'Add some feature'
) - Push to the branch (
git push origin my-new-feature
) - Create new Pull Request