Integrate BigBlueButton with ILIAS

01

Choose the supported integration path

ILIAS integrations are delivered through plugins whose compatibility follows specific ILIAS branches. Select an actively maintained release from the ILIAS plugin ecosystem, read its version matrix and deploy it through the normal ILIAS plugin administration workflow.

• Exact ILIAS version and plugin compatibility verified.
• Filesystem/deployment access plus ILIAS administrator rights.
• BBB/Scalelite endpoint and a staging 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 ILIAS

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 the selected plugin in the path and version documented by its maintainer.

2. 2

   Complete database/plugin update steps in ILIAS administration.

3. 3

   Enter BBB URL and secret in server-side plugin configuration.

4. 4

   Enable the plugin only for a pilot course and map tutor/member permissions.

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

   Create and join as tutor and member.

2. 2

   Check room reuse, maximum participants and moderator assignment.

3. 3

   Record a short meeting and verify listing/playback.

4. 4

   Deactivate a user and verify old course links no longer grant access.

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.

• A plugin screen missing after upload usually means path, branch or ILIAS-version mismatch.
• API checksum failures can follow a copied endpoint without the required path.
• Review plugin maintenance activity before every major ILIAS upgrade.

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.