2fb26ff0cf
This patch includes two improvements made for bbb-web. It tries to better isolate the sessionToken's handling and session's validation, including logs for each one of these steps; and removes maxParticipats control from registered users (that are no longer removed from bbb-web collections) binding it to joined users or users that reached the enter API call. The following adds more details about this last one: User's regular flow to join a meeting goes around an API join call -> redis register event -> redirect to client page -> API enter call -> redis join event. When the guest policy is ASK_MODERATOR, non-moderators are registered and redirected to a guest lobby that polls for her/his guest status and only enters the meeting after a moderator approval. Using registered users as control to check how many participants are in a meeting is problematic because non-approved guests are counted as participants and bbb-web has to find out when to ditch registered users records to make a seat in a meeting available again. In other words, a meeting with maxParicipants of 5 can get it's joins locked with a moderator and 4 waiting guests or bbb-web can wrongly drop a registered user record on a reconnection inducing weird 401 responses from the API. This change proposes to control maxParticipants both at join and enter API calls monitoring the number of redis joined users. This also includes an extra buffer to capture users that called the enter API but still don't have an user joined event. User left events are now handled different holding the user data before removing from the joined users collection and only releasing after verifying that the user didn't reconnected. Both user left timeout `usersTimeout` and entered user timeout `enteredUsersTimeout` can be configured at properties. |
||
|---|---|---|
| .. | ||
| project | ||
| scala | ||
| src | ||
| .gitignore | ||
| .scalariform.conf | ||
| build.sbt | ||
| deploy.sh | ||
| Dockerfile | ||
| README.md | ||