RocketChat / RocketChat/Rocket.Chat
BigBlueButton integration not working
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
The BigBlueButton integration in RC is not working. Users are authenticated on RC aswell as on bbb using openLDAP (the LDAP for the both of them)
Steps to reproduce:
Installed my own bbb server, everything is working fine on the instance, but when I activate the bbb integration in rocketchat and try to start a video call from a channel, the sidebar pops up with the "Start Meeting" button" but when you click on it, nothing happens
Expected behavior:
A bbb video call window should popup and start a video conference
Actual behavior:
nothing except an error in the devtools
Server Setup Information:
- Version of Rocket.Chat Server: 1.0.3
- Operating System: Ubuntu 18.04
- Deployment Method: snap
- Number of Running Instances: 1
- NodeJS Version: NA
- MongoDB Version: NA
Additional context
All instances are in the AWS env, the LDAP, the RC and the bbb
the bbb insstance and the RC instance authenticate users from the same LDAP
Relevant logs:
Client logs :
"Error: Internal server error [500]
at w._livedata_result (https://chat.exemple.io/c9b63b63818b7389d550732abac3e2edcb8831da.js?meteor_js_resource=true:59:17834)
at w.onMessage (https://chat.exemple.io/c9b63b63818b7389d550732abac3e2edcb8831da.js?meteor_js_resource=true:59:20175)
at https://chat.exemple.io/c9b63b63818b7389d550732abac3e2edcb8831da.js?meteor_js_resource=true:57:2772
at Array.forEach (<anonymous>)
at l.forEachCallback (https://chat.exemple.io/c9b63b63818b7389d550732abac3e2edcb8831da.js?meteor_js_resource=true:57:3967)
at k.socket.onmessage (https://chat.exemple.io/c9b63b63818b7389d550732abac3e2edcb8831da.js?meteor_js_resource=true:57:2742)
at k.r.dispatchEvent (https://chat.exemple.io/c9b63b63818b7389d550732abac3e2edcb8831da.js?meteor_js_resource=true:57:6474)
at k._dispatchMessage (https://chat.exemple.io/c9b63b63818b7389d550732abac3e2edcb8831da.js?meteor_js_resource=true:57:20111)
at k._didMessage (https://chat.exemple.io/c9b63b63818b7389d550732abac3e2edcb8831da.js?meteor_js_resource=true:57:21011)
at WebSocket.o.ws.onmessage (https://chat.exemple.io/c9b63b63818b7389d550732abac3e2edcb8831da.js?meteor_js_resource=true:57:23160)"
Server logs :
2019-05-22T07:21:00Z rocketchat-server.rocketchat-server[24110]: at Array.forEac
h (<anonymous>)
2019-05-22T07:21:00Z rocketchat-server.rocketchat-server[24110]: at ldap.searchU
sersSync.Meteor.bindEnvironment (app/ldap/server/sync.js:290:13)
2019-05-22T07:21:00Z rocketchat-server.rocketchat-server[24110]: at runWithEnvir
onment (packages/meteor.js:1356:24)
2019-05-22T07:21:00Z rocketchat-server.rocketchat-server[24110]: isClientSafe: tru
e,
2019-05-22T07:21:00Z rocketchat-server.rocketchat-server[24110]: error: 'LDAP-logi
n-error',
2019-05-22T07:21:00Z rocketchat-server.rocketchat-server[24110]: reason: 'LDAP Aut
hentication succeded, there is no email to create an account. Have you tried setting
your Default Domain in LDAP Settings?',
2019-05-22T07:21:00Z rocketchat-server.rocketchat-server[24110]: details: undefine
d,
2019-05-22T07:21:00Z rocketchat-server.rocketchat-server[24110]: message: 'LDAP Au
thentication succeded, there is no email to create an account. Have you tried settin
g your Default Domain in LDAP Settings? [LDAP-login-error]',
2019-05-22T07:21:00Z rocketchat-server.rocketchat-server[24110]: errorType: 'Meteo
r.Error' }
The default domain is set in the LDAP settings, I don't understand why this warning is in the logs
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the BigBlueButton meeting failure and reviewing the LDAP error reported at app/ldap/server/sync.js:290, along with the client 500 response. Trace how the LDAP account is created when the BBB integration starts. Done means the cause is identified and a verified configuration or code fix allows the meeting window to start successfully.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100