Pilot — first trackInstructure

Add NAVI to Canvas

Canvas registers external tools through an LTI Developer Key, created at the account level. Once the key exists and is turned ON, you install the tool into a sub-account or course using its Client ID.

Verified against: Canvas LMS, cloud release — not yet verified against a live instance

This integration is not live yet

NAVI's LTI 1.3 endpoints are in development. This guide is published now so your team can review the approach, the data we request, and the security posture before committing time. The URLs below are the ones we will use; they are not yet serving traffic. Pilot institutions get them working with us directly.

What you will need from NAVI

These are identical for every institution — there is nothing per-tenant to look up.

OIDC login initiation URLhttps://partnernavi.geo-ed.tech/api/lti/login
Redirect / launch URLhttps://partnernavi.geo-ed.tech/api/lti/launch
Public JWKS URLhttps://partnernavi.geo-ed.tech/api/lti/jwks
Deep Linking URLhttps://partnernavi.geo-ed.tech/api/lti/launch
Target Link URIhttps://partnernavi.geo-ed.tech/api/lti/launch

What we will need from you

  • Issuer (platform ID)
  • Client ID
  • Deployment ID(s)
  • Platform JWKS / keyset URL
  • OIDC authentication endpoint
  • OAuth2 token endpoint

Canvas displays all of these on the registration confirmation screen.

Setup steps

  1. 1

    Admin → Developer Keys → + Developer Key → + LTI Key

    You must be a Canvas account admin. Choose "Enter URL" or "Paste JSON" — we generate the JSON for you so there is nothing to hand-type.

  2. 2

    Paste the NAVI configuration JSON

    This sets the target link URI, OIDC initiation URL, JWKS URL, and placements in one action. In the pilot we send you this file directly.

  3. 3

    Turn the key state to ON

    A key defaults to OFF after creation. This is the single most common reason a first launch fails with an unauthorized error.

  4. 4

    Copy the Client ID

    The number shown in the Details column. Send it to us — it is the client_id half of your registration.

  5. 5

    Install into a sub-account or course

    Settings → Apps → View App Configurations → + App → By Client ID, paste, Submit.

  6. 6

    Run a test launch before telling teachers

    Place the tool in a sandbox course and launch as a test student.

Field-name translation

Every LMS names the same LTI concepts differently. This is the table that saves the argument.

Canvas calls itWe call it
Target Link URILaunch URL
OpenID Connect Initiation UrlLogin initiation URL
JWK Method → Public JWK URLOur JWKS URL
Client IDclient_id
Deployment IDdeployment_id
Issuer (always https://canvas.instructure.com)issuer

Known gotchas

  • !The issuer is https://canvas.instructure.com for every Canvas instance — including self-hosted. Registrations must therefore be told apart by client_id and deployment_id, never by issuer alone.
  • !A newly created Developer Key is OFF by default.
  • !Each place you install the tool produces its own deployment_id. All of them need registering, or those launches are rejected.
  • !Canvas Free-for-Teachers supports Developer Keys, so a pilot can be tested at zero cost.
  • !Our v1 requests no AGS or NRPS scopes. The scopes array is intentionally empty — adding scopes later requires re-approval by your admin, which we would rather do once, deliberately.

Free test environment

Canvas Free-for-Teachers (canvas.instructure.com/register) supports LTI Developer Keys at no cost.

Something here out of date, or not working?

LMS interfaces change and guides rot. If a step does not match what you are seeing, tell us and we will fix the page — include your Canvas version if you can.