why: Collaborations edit launches seem to be matching via the tool's
associated dev key domain instead of the tool that created the
collaboration. This can be problematic if 2 Developer Keys sharing the
same domain are installed.
fixes INTEROP-8865
flag=none
test plan:
- prerequisites: have two developer keys (and associated tools) with
the same domain.
- create a course collaboration with each of the tools
- in a rails console find your collaboration(s) and update it to make it
editable, like: `collab.data["updateUrl"] = "http://lti13testtool.docker/launch?deep_link_location/DX5etdRmlBw_edit"
collab.save!
- visit course collaborations in the UI
- each of the collaborations displayed should have `data-update-launch-url`
that contains `...retrieve?client_id=<global_id_of_assoc_tool's_dev_key>&...`
Change-Id: Id105911fc1da889e6b9a9f540cac761b77f9c164
Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/360818
Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com>
Reviewed-by: Tucker Mcknight <tmcknight@instructure.com>
QA-Review: Tucker Mcknight <tmcknight@instructure.com>
Product-Review: Alexis Nast <alexis.nast@instructure.com>
17cea5c48a