LTI Pro - Canvas API Breaking Changes

Zoom Apps
1

Per official Instructure communications all HTTP requests, including LTI and API ones must have a user-agent header by January 17th.

Instructure has provided a report to all LMS administrators that identifies developer keys that are not providing a user-agent header. Both the LTI developer key and the LTI API key for Zoom LTI Pro are reported to not be providing the header.

I have filed two Support tickets where I’ve been told that it’s not their problem, but come January 17th, it seems like it will be.

2

Hi @David41
Thanks for reaching out to us and welcome to the Zoom Developer forum.
Could you please share with me the support ticket number so I can take a closer look to it

4

Here you go: TS2103709

Second ticket I’ve filed. Still not sure they understand the problem and the urgency of it.

5

Hi @David41
Thank you so much for your patience.
I was able to connect with the developer of this integration, and they confirmed that we’re implementing these changes in our December release*. This issue should be resolved next month.

6

Thanks. I heard the same in the community. Still not sure what was wrong with the tickets I filed.

7

@David41 I will bring it up with the Support team to make sure these kind of requests do not get routed to the Dev forum

8

Do we know if the change did make it in December? I was looking at the Release Notes page, but its very out of date. Release notes for LTI Pro

9

Based on the latest report I ran within Canvas, yes, it appears that it did.