How QCLF Secures Managed Host Live Without Storing LiveKit Secrets

QCLF does not ask site owners to store permanent LiveKit server API credentials in Joomla. Instead, the extension proves the installation and current entitlement to QuantaCade’s managed control plane, signs short-lived authorization requests locally, and receives room-scoped realtime connection details.

The browser receives only the managed realtime URL and a short-lived participant token needed for that Host or viewer connection.

Installation Signing Identity

When first needed, QCLF creates an EC P-256 installation key pair. The private key is encrypted with the QuantaCade secret store; the public key/fingerprint is saved for enrollment. Authorization payloads are signed locally with SHA-256 and the private key is not sent as the realtime credential.

Enrollment and Entitlement Proof

Enrollment includes the normalized site domain, installation UUID, product/version information, public key, and current entitlement proof. Host Live requires a healthy entitlement task plus an effective Pro/Max/All Access tier appropriate to the live session type.

Short-Lived Signed Requests

Authorization payloads include the installation/client identity, domain, product, timestamp, a 120-second request TTL, nonce, correlation ID, room/session/topic context, and participant role. QCLF signs the JSON before sending it to the HTTPS control API.

Room-Scoped Browser Credentials

The managed response must contain a secure wss:// realtime URL, a valid token-shaped participant credential, its expiration metadata, and the exact Host identity. Those are returned to the browser for the current room connection; they are not permanent LiveKit server secrets.

Failure Is Fail-Closed

If enrollment, signature, entitlement, managed authorization, or returned connection details are invalid, Host Live refuses to connect. A client/key mismatch triggers controlled re-enrollment instead of silently accepting stale identity.

Room Cleanup

When the live Topic ends, QCLF sends a separately signed managed room-end request where possible. The forum lifecycle remains authoritative even if transient managed-room cleanup fails.

Community Discussion

Want to compare forum workflows, share practical QCLF tips, or discuss how other Joomla site owners use this feature? Visit the QC Live Forum Community. For private support, bug reports, account-specific entitlement problems, or feature requests, use the QuantaCade support system.