it is useful when the application that requires authorization wants to inject user information to the request
it can be an integration with a third party applicaton and it will require to receive user-external-is and meeting-external-id
it can also validate if the requester is moderator or presenter, so now it includes user-is-moderator and user-is-presenter headers
* Fix: allow CORS requests to graphql API
In cluster setups the Graphql API endpoints are fetched as a CORS
request. We need to allow that.
* Fix: Allow CORS requests to ping endpoint
In cluster setups the ping is sent directly to the BBB server. So it
needs to allow CORS requests for cluster setups.
* Fix: construct relative API path for cluster setups
* Fix: adjust docs for cluster setup
As bbb-html5 client is static, setup instructions for cluster setup have
to be changed accordingly.
* Fix docs: remove superfluous ```yaml
This must have been introduced by accident.
---------
Co-authored-by: Daniel Schreiber <daniel.schreiber@hrz.tu-chemnitz.de>
Starts supporting the param enforceLayout, a subsequent PR will finish and document it
Starts supporting user-session-metadata, a subsequent PR will finish and document it
Additionally, the mobile app can use this feature to render the whiteboard inside an iframe with the same `userId`.
By setting the parameter `revokePreviousSession=true`, a new `sessionToken` will be generated, and the previous session will be revoked when the new device connects. This is useful for transferring a session to another device and automatically closing the previous session.
* Add graphql API endpoint to BBB API
This parameter will be required for the HTML5 client to discover the API
endpoint of the GraphQL API so it can fetch its settings.
* Fix: ensure API calls are headed towards the BBB Server
In a cluster setup the URL that is visible in the browser is different
from the URL of the BBB Server.
The clients needs to contact the BBB server to retrieve information
about the graphQL websocket and the graphql API.
This patch adds the GraphQL API endpoint to the BBB API and changes the
Client to use it.
* Make GraphQL API endpoint configurable
The default value should work for single node and cluster setups
* Update docs to reflect changes required by cluster setup
* fix eslint and typescript errors
* Fix cluster setup docs
- add missing parts for hasura
- use consistent domain example.com
* rename variable
Co-authored-by: Gustavo Trott <gustavo@trott.com.br>
* rename variable
Co-authored-by: Gustavo Trott <gustavo@trott.com.br>
* rename variable
Co-authored-by: Gustavo Trott <gustavo@trott.com.br>
* Update bigbluebutton-web/grails-app/controllers/org/bigbluebutton/web/controllers/ApiController.groovy
Co-authored-by: Gustavo Trott <gustavo@trott.com.br>
* Update bigbluebutton-web/grails-app/conf/bigbluebutton.properties
Co-authored-by: Gustavo Trott <gustavo@trott.com.br>
---------
Co-authored-by: Daniel Schreiber <daniel.schreiber@hrz.tu-chemnitz.de>
Co-authored-by: Gustavo Trott <gustavo@trott.com.br>
* feature: Introduces API /sendChatMessage endpoint
* only allow GET requests for sendChatMessage
---------
Co-authored-by: Anton Georgiev <antobinary@users.noreply.github.com>
