PlannedD2L

Add NAVI to D2L Brightspace

Brightspace has solid LTI Advantage and Dynamic Registration support. Its one strict behaviour is exact-match validation on redirect URLs — a trailing slash is enough to break a launch.

Verified against: Brightspace LTI Advantage flow — 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

D2L Brightspace displays all of these on the registration confirmation screen.

Setup steps

  1. 1

    Admin Tools → Manage Extensibility → LTI Advantage → Register Tool

    You need the appropriate administrator permission.

  2. 2

    Choose Dynamic or Standard registration

    Dynamic is faster. Standard means entering our URLs by hand.

  3. 3

    Enter the NAVI URLs exactly

    Copy and paste — do not retype. Brightspace matches redirect URLs exactly.

  4. 4

    Enable the tool and set the deployment

    Then add it to the org units that should have access.

  5. 5

    Test before announcing

    Launch as a student in a sandbox org unit.

Field-name translation

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

D2L Brightspace calls itWe call it
Redirect URLsLaunch URL — must match exactly
OpenID Connect Login URLLogin initiation URL
Keyset URLOur JWKS URL
Client IDclient_id
Issuerissuer
Deployment IDdeployment_id

Known gotchas

  • !Redirect URL matching is exact. A trailing slash, http vs https, or a differing subdomain will fail the launch.
  • !Deployments are scoped per org unit, so a large institution will produce several deployment_ids.
  • !Dynamic Registration requires outbound HTTPS from Brightspace to our endpoints.

Test environment

D2L provides developer sandboxes through their partner community on request.

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 D2L Brightspace version if you can.