I've noticed that deep linking launch is using Tool Launch URL instead of Deep Linking Launch URL. I found this behavior when deep linking launch for a tool named ChemVantage was not working. Deep linking started working when i replaced the too launch URL with deep linking one.
I've seen this issue for on-the-block configuration. I have not tested this with LTI store.
To reproduce, choose 2 different URLs and add one in tool launch URL and the other in deep linking launch. Now perform the deep linking launch from Studio and decode the id_token used in the launch. The claim https://purl.imsglobal.org/spec/lti/claim/target_link_uri will tell you which field the URL is fetched from for LtiDeepLinkingRequest.
I've noticed that deep linking launch is using
Tool Launch URLinstead ofDeep Linking Launch URL. I found this behavior when deep linking launch for a tool named ChemVantage was not working. Deep linking started working when i replaced the too launch URL with deep linking one.I've seen this issue for on-the-block configuration. I have not tested this with LTI store.
To reproduce, choose 2 different URLs and add one in tool launch URL and the other in deep linking launch. Now perform the deep linking launch from Studio and decode the
id_tokenused in the launch. The claimhttps://purl.imsglobal.org/spec/lti/claim/target_link_uriwill tell you which field the URL is fetched from forLtiDeepLinkingRequest.