frontend: add End-to-End Encryption (E2EE) - Updated meeting lobby and room wizard components to handle E2EE settings. - Added E2EE configuration options in the room wizard and lobby services. - Implemented validation for E2EE key input in participant forms. - Enhanced UI to reflect E2EE restrictions on recording and streaming. - Added animations for E2EE warning and info sections. backend: Added E2EE configuration and middleware backend: Added e2ee configuration property to openapi Enables E2EE functionality Configures the application to support end-to-end encryption (E2EE). Copies the necessary worker script to the assets folder. Passes the E2EE key to the meeting component. Adds a script to remove node_modules and dist folder. frontend: Add E2EE UI tests and configuration options webcomponent: Ensure cleanup of test environment after moderation tests frontend: Update E2EE description and restrictions webcomponent: Enhance E2EE UI tests by adding participant interactions and verifying visibility with correct keys backend: Updated start recording example response
9 lines
267 B
YAML
9 lines
267 B
YAML
description: Forbidden - Insufficient Permissions
|
|
content:
|
|
application/json:
|
|
schema:
|
|
$ref: '../schemas/error.yaml'
|
|
example:
|
|
error: Authorization Error
|
|
message: 'Insufficient permissions to access this resource'
|