During a deep link launch, the target_link_uri is set to the lti_1p3_launch_urlhere as opposed to the lti_advantage_deep_linking_launch_url.
I believe we want to be using the lti_advantage_deep_linking_launch_url as the target_link_uri during deep link launch since the normal launch url would be associated with a specific resource link (whereas during deep linking there may not even be a resource link created yet).
The redirect_uri is then set to the deep linking launch url instead of respecting (and validating) the redirect_uri returned by the Tool.
I believe we should respect the Tool provided redirect_uri (assuming it's in our validate redirect uri's list).
target_link_uri
is set to thelti_1p3_launch_url
here as opposed to thelti_advantage_deep_linking_launch_url
.lti_advantage_deep_linking_launch_url
as thetarget_link_uri
during deep link launch since the normal launch url would be associated with a specific resource link (whereas during deep linking there may not even be a resource link created yet).redirect_uri
is then set to the deep linking launch url instead of respecting (and validating) theredirect_uri
returned by the Tool.redirect_uri
(assuming it's in our validate redirect uri's list).