LTI 1.3 Deep Linking Issues

Site Operators
1

We have dozens of successful LTI 1.1/1.0 implementations, as it’s a simple config. But we don’t have any LTI 1.3 implementations, as we keep running into issues at every corner. Our current issue is the handoff. We received similar issues from two vendors:

Vendor 1
Invalid LTI Launch Type.
Status: 422 – Message_Key: InvalidLaunchType

Vendor 2
Error Code: LTI_13_CLAIMS_MISMATCH

I know we are missing something but maybe another set of eyes. Our payload (scrubbed) is:

“payload”:{
“xxxxx/spec/lti/claim/message_type”:“LtiResourceLinkRequest”
“xxxxx/spec/lti/claim/version”:“1.3.0”
“iss”:“https://xxxxxxx”
“aud”:“xxxxxxx”
“azp”:“xxxxxxx”
“xxxxx/spec/lti/claim/deployment_id”:“1”
“xxxxx/spec/lti/claim/target_link_uri”:“xxxxxxx”
“sub”:“xxxxxxx”
“xxxxx/spec/lti/claim/roles”:[
0:
“xxxxx/vocab/lis/v2/institution/person#Student”
]
“name”:“xxxxxxx”
“given_name”:“xxxxxx”
“family_name”:“xxxxxxx”
“xxxxx/spec/lti/claim/resource_link”:{
“id”:“block-xxxxxxx”
}
“xxxxx/spec/lti/claim/launch_presentation”:{
“document_target”:“iframe”
}
“xxxxx/spec/lti/claim/context”:{
“id”:“coursexxxxxxx”
“type”:[…
]
“title”:“xxxxxxx”
“label”:“coursexxxxxxxC”
}
“hxxxxxxx”:{
“book_location”:“xxxxxxx”
}
“nonce”:“xxxxxxx”
“iat”:1xxxxxxx
“exp”:xxxxxxx
}

Would appreciate any advise.