The Instructure Community will enter a read-only state on November 22, 2025 as we prepare to migrate to our new Community platform in early December.
Read our blog post for more info about this change.
We're a content publisher and we've recently run into a couple of schools where the need to go to the Developer Keys area in Canvas to implement LTI 1.3 has raised red flags about what information they're exposing to vendors.
My guess is that the LTI Key lives with the Developer Keys because that's where the OAuth2 authentication lives, but it's not really a Developer Key in the traditional sense. Is there an official document that explains this? If not, can someone make one? It would help remove a roadblock to vendors integrating with Canvas.
I think this is a good thing that schools are looking deeper into data 3rd parties are asking for from LMS platforms like Canvas. You're right this developer key is used in Canvas to create the client_id used for the Open ID Connect authentication flow in LTI 1.3.
I'm going to be generating blog posts and more documentation in the coming months, but for now the closest documentation we have is
How do I configure an LTI key for an account?
Thanks for sharing this feedback.
Thanks, Karl, I'm looking forward to it!
Community helpTo interact with Panda Bot, our automated chatbot, you need to sign up or log in:
Sign inTo interact with Panda Bot, our automated chatbot, you need to sign up or log in:
Sign in
This discussion post is outdated and has been archived. Please use the Community question forums and official documentation for the most current and accurate information.