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.
Found this content helpful? Log in or sign up to leave a like!
Canvas is not able to find "OpenID Connect Initiation URL" from the LTI 1.3.
In my case I have developed a provider which is based on LTI1.3 IMSGLOBAL standard. So when trying to launch the url link , Canvas is sending proper access token request with parameters (clientID, login_hint,target_link_uri,lti_message_hint,canvas_region) to the LTI but unfortunately OidcLogin file is giving us 404 error due to which LTI is not able to request for ID Token.
Solved! Go to Solution.
I recently completed an LTI 1.3 integration for Learning system called OpenDSA
When that happens the root cause is always one (or both) of:
Tool doesn’t expose the route : the path exists in configuration but your web server / framework has no handler mapped for it (e.g., typo, wrong HTTP, bad base-path, behind a firewall) make sure tool exposes the route, try expose your local tool via HTTPS or get a deployment server so it can access some traffic. (you need a publicly reachable HTTPS URL).
Hopefully this helps.
Hello @citv257
Sorry that you having trouble with your LTI. Thanks for posting this in the global Canvas Community.
It sounds like there might be something going on with the configuration of the tool when you launch it. What is the LTI are you using when this happens?
-Colton
I recently completed an LTI 1.3 integration for Learning system called OpenDSA
When that happens the root cause is always one (or both) of:
Tool doesn’t expose the route : the path exists in configuration but your web server / framework has no handler mapped for it (e.g., typo, wrong HTTP, bad base-path, behind a firewall) make sure tool exposes the route, try expose your local tool via HTTPS or get a deployment server so it can access some traffic. (you need a publicly reachable HTTPS URL).
Hopefully this helps.
Had a similar issue a while back, turned out the problem was with how the OIDC login endpoint was registered in the platform. Double-check the exact URL you gave Canvas for the OIDC initiation; even a small mismatch (like a missing slash or wrong casing) can cause that 404. Also worth checking if the route is actually being served and isn’t restricted by a framework/router config.
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