Problem with deep linking lti in test.instructure?

[theaht123]

Hello,

We are experiencing problems with running custom tools (lti 1.3) with deep linking, on the test server (<our-instance>.test.instructure.com).

It seems that the message we post to platform storage is not receieved.

Everything works on the production server (<our-instance>.instructure.com). Is anyone else experiencing problems with deep linking lti on your test server?

[matthew_buckett]

Have you updated the configuration so that the audience for your deep linking response is the test server rather than be production server?

For example in production you would normally have this claim in your JWT:

  "aud": "https://canvas.instructure.com",

but on beta it should be:

  "aud": "https://canvas.beta.instructure.com",

and test should just have beta replaced with test. Our tool that uses deep linking is working fine on beta, I can't check on the test instance as we don't have them configured for that instance, but expect it's working.

Have you ever had your code working against the test instance or has it recently stopped working?

[theaht123]

Thank you. 

Yes, we have updated the config to the test sever. 

It has been working before, we believe it might have stopped working after the update of the OIDC endpoints.

However after updating the the endpoints (https://sso.test.canvaslms.com..) and lti_storage_target (post_message_forwarding), we are still not able to send the message, or we do not receieve the response.