Integrate BigBlueButton with Brightspace

01

Choose the supported integration path

Brightspace is LTI-capable and BigBlueButton’s LTI framework is the generic bridge. The BBB broker currently documents both legacy key/secret launches and manual LTI 1.3 registration; agree the exact version and supported Advantage services with D2L security owners before production.

• Brightspace Manage Extensibility permission.
• Compatible LTI version agreed by both products.
• Dedicated registration scope and test course.

02

Prepare BigBlueButton and credentials

Use a production BigBlueButton endpoint with a trusted TLS certificate. Keep the API shared secret or LTI secret on the server side: it is equivalent to an application credential and must never be placed in browser code, a public repository or a screenshot.

1. 1

   Confirm the BigBlueButton server is healthy and that its public hostname resolves correctly.

2. 2

   Retrieve the API URL and shared secret with sudo bbb-conf --secret, or create a dedicated LTI key and secret where the integration uses LTI.

3. 3

   Record the platform version, connector version, owner and rollback point before making the change.

sudo bbb-conf --check
sudo bbb-conf --secret

03

Configure Brightspace

Make the first connection in a staging course, workspace or tenant. Use a dedicated test teacher and test learner so role mapping can be observed rather than inferred from an administrator account.

1. 1

   Install and verify BBB’s LTI endpoint.

2. 2

   In Brightspace, register the tool using the launch URL and dedicated credentials.

3. 3

   Limit security/role information sent to what the classroom requires.

4. 4

   Create a link in a sandbox course and set visibility for the intended roles.

04

Run an end-to-end acceptance test

A green “connection successful” message proves only that one API request worked. The useful test follows the complete classroom lifecycle from creation through recording publication.

1. 1

   Launch as instructor, teaching assistant and learner.

2. 2

   Verify the launch opens in the intended window and survives privacy settings.

3. 3

   Check name, role and course-context mapping.

4. 4

   Test meeting end and the chosen recording-return workflow.

05

Common problems and practical fixes

Start with timestamps, browser developer tools and the logs on both sides. Repeatedly replacing secrets rarely fixes a hostname, TLS, role or callback problem and makes the evidence harder to follow.

• “Tool consumer” errors point to registration or signing mismatch.
• Browser blocks may require an external-window launch instead of iframe.
• LTI launch success does not imply automatic grade or recording return.

06

Production hardening and upgrades

Restrict who can create rooms, define recording retention, test accessibility and document the integration owner. Pin or approve connector updates, subscribe to upstream releases and repeat the acceptance test after changes to the LMS, connector, BigBlueButton or reverse proxy.

• Do not expose the BigBlueButton shared secret to course authors or client-side JavaScript.
• Use least-privilege teacher roles and test guest, suspended and unenrolled users.
• Monitor API errors, failed joins, recording processing and disk growth.
• Keep a short rollback runbook: previous package, configuration backup and maintenance window.