Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

getJoinMeetingURL() should not be deprecated, and joinMeeting() should not exist. #261

Open
defnull opened this issue Jul 21, 2024 · 0 comments

Comments

@defnull
Copy link

defnull commented Jul 21, 2024

The standard flow for letting a user join a meeting is to create the meeting, generate a join URL and redirecting the user to that join URL. The join response will set an essential session cookie and then redirect the user a second time to the actual htm5 web client URL.

The current BigBlueButton class makes this unnecessary hard and counterintuitive. getJoinMeetingURL() is deprecated, so you have to jump through hoops to get a valid join URL (e.g. $bbb->getUrlBuilder()->getJoinMeetingURL($joinMeetingParams);). The wiki does not explain this and instead uses the now deprecated API.

Developers instead find the joinMeeting($joinMeetingParams) method and think this is the correct way to let a user join a meeting. It is not. The user is now missing the session cookie and developers have to disable security features (via allowRequestsWithoutSession=true) to make it work. It is almost never the correct way to resolve the join link server-side, but that's the most obvious way the current BigBlueButton class suggests. The mailing-list is full of questions from developers that fall into this trap, and they often do not get the correct answer.

Please de-deprecate getJoinMeetingURL() and add a clear warning label to the joinMeeting method documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant